DownForAI

Claude Chat status: API, auth, latency & outage reports

Claude Chat is operational right now. Last tracked incident: July 29, 2026. DownForAI checks 1 monitored surface every ~75 minutes.

Operational
Last probe 7 min ago·1 surface
Official statusHigh confidence
📡 Official status page →📚 Docs →💳 Pricing →
100.0%
24h Uptime
267ms
p50 Network Latencyⓘ
502ms
p95 Network Latencyⓘ
1
Incidents (30d)

DownForAI monitors Claude Chat via a single endpoint — Claude.ai Web. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 267 ms; p95: 502 ms.

Claude Chat had 1 tracked incident over the last 30 days. The most recent was logged on July 29, 2026 ("claude-chat experiencing issues", lasting 60 min).

Data confidence: HighLast checked 7 min ago · 1 monitored surface · 1 with 24 h latency data

Current Status

✅
Operational
Everything works normally
✓Checked by our probes · 259ms
Verified 6m ago
✓No major incident reported
ⓘNo reports in the last 24h

Having issues?

Help other users by reporting if Claude Chat is not working for you.

0reports in the last 24 hours

Surface Health

Claude.ai WebOperational
HTTP 200p50 267ms6m ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about Claude Chat

No confirmed provider-side issue detected
DownForAI currently sees Claude Chat as operational based on available monitoring signals.
Signal source: official status API · Monitoring confidence: High
Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

1 incident
claude-chat experiencing issues
Resolved
Jul 29, 21:30· 1hMAJOR
Our monitoring detected that claude-chat may be experiencing an outage.

Reported symptoms

No user reports for Claude Chat in the last 24 hours.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

Claude is Anthropic's AI assistant focused on safety and long-context reasoning. The consumer-facing product lives at claude.ai. For developer API access, see the separate Anthropic API card.

What we monitor
claude.ai — Consumer web interface
Claude mobile apps — Mobile backend
Auth (claude.ai sign-in) — Authentication
Status page segments
claude.aiClaude APIClaude Console (platform.claude.com)Claude Code
Model families
Claude Opus 4.6, Claude Opus 4.1, Claude Opus 4Claude Sonnet 4.6, Claude Sonnet 4.5, Claude Sonnet 4Claude Haiku 4.5Claude Sonnet 3.7 (deprecated but still seen in legacy integrations)
Common limits & quotas
  • claude.ai usage limits vary by plan and load; official exact caps are not publicly fixed and change with load
  • Pro, Max, Team, Enterprise tiers available; consult pricing page for current plans
Ecosystem dependencies
Cursor, Continue.dev, Zed, Claude Code — all route workloads to Claude models by default in many configurationsEnterprise SaaS products often consume Claude via AWS Bedrock or Google Vertex AI rather than direct APIDirect Anthropic API and Bedrock/Vertex-hosted Claude are separate infrastructures with different reliability profiles
Operator notes
  • Direct Anthropic API and Bedrock-hosted Claude are different infrastructures. Bedrock can stay up during direct API outages.
  • Model aliases and provider-specific model IDs differ across Claude API, Bedrock, and Vertex — a 'model not found' error may just be a cross-platform ID mismatch
  • For long-context workloads (>100k tokens), Sonnet often has better availability than Opus during capacity incidents
  • Claude Code has its own status component separate from claude.ai
Diagnostic signals
$ Visit status.anthropic.com — verify which component is affected (claude.ai, Claude API, Claude Code, Console)$ For API diagnostic, see the separate Anthropic API card

Fallback alternatives

What to use if this service is down

claude.ai is degraded but API works
API Console Workbench at platform.claude.com can reduce downtime for power users
Easy switch
Direct Anthropic path is degraded and org has Bedrock/Vertex provisioned
AWS Bedrock or Google Vertex AI (separate infrastructures hosting Claude)
Easy switch
All Anthropic routes unavailable
OpenAI ChatGPT / Mistral Le Chat can reduce downtime for general chat
Easy switch
Claude-specific reasoning workloads
Google Gemini 2.5 Pro is a close equivalent
Easy switch

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Claude Chat statusEmbed this status badgeREADME · docs ▾
Markdown
[![Claude Chat status](https://downforai.com/api/badge/claude-chat.svg)](https://downforai.com/claude-chat)
HTML
<a href="https://downforai.com/claude-chat"><img src="https://downforai.com/api/badge/claude-chat.svg" alt="Claude Chat status" /></a>

Community Discussion

0/1000
No comments yet. Be the first to share your experience!

Still having issues with Claude Chat?

Let the community know and help others experiencing the same problem.