Elevated errors on Opus 4.5
Claude API (api.anthropic.com)
Why Is Claude So Slow Today?
Check whether slow Claude replies, delayed Claude Code runs, usage-limit symptoms, timeouts, or sluggish API responses match a recent incident or a local setup issue.
Current answerClaude is currently operational according to the official Claude status page.
Likely impactSlow replies, timeouts, delayed API responses, Claude Code lag, or file upload delays
Next checkCheck the affected surface first: Claude.ai, API, Claude Code, or your network.
Fast answer
Claude slow diagnosis
If Claude is slow but not fully down, separate the symptom into service latency, account limits, local Claude Code context, or API errors before changing prompts or retry logic.
Service degradation
Slow across Claude.ai, API, and Claude Code, especially after a recent incident.
Limits or quota
Requests still work, but responses feel throttled, delayed, or model access changes.
Claude Code context
Slow only in one repository, terminal, long session, MCP setup, or large context.
API errors
Request timed out, stream idle timeout, 429, 529 overloaded, 500, or 503 errors need log-based triage.
Claude slow but status says operational
A green status page does not always mean every Claude workflow is fast. Claude can be officially operational while a specific model, account, browser session, region, prompt, API route, or Claude Code run is still slow.
- If Claude.ai is slow but API calls are normal, test another browser, private window, network, and account.
- If Claude Code is slow, compare repository size, context length, tool calls, model choice, and terminal or IDE state.
- If API and Claude Code are both slow, check Claude API status, recent model incidents, request logs, and retry behavior.
- If Claude takes long to respond and logs show request timed out or stream idle timeout, use the Claude API timeout checklist.
- If slow replies began after a recent incident, wait for recovery to stabilize before changing prompts, retries, or fallback logic.
Claude Code slow troubleshooting checklist
Use this checklist when Claude Code feels slow, degraded, lazy, worse than usual, or takes forever. The cause may be a service incident, but it may also be usage limits, long context, a large codebase, model routing, or too many tool calls.
- Compare Claude Code status with Claude API status.
- Check whether slow runs happen only with long context, large repositories, or many tool calls.
- Review usage limits, API rate limits, authentication state, model choice, network route, and retry behavior.
- Try the same task with a smaller file set or narrower prompt to separate Claude latency from workflow size.
- If Claude is slow across web, API, and Claude Code, check Claude Status and recent incidents.
Claude Code slow on Windows, terminal, or long sessions
If Claude Code is slow only in one terminal, OS, repository, or long-running session, treat it as a local workflow diagnosis before treating it as a full Claude service incident.
- Try a fresh Claude Code session to rule out long context, compaction, or stale terminal state.
- Compare PowerShell, Git Bash, Terminal, or another shell if typing, menus, or tool calls feel delayed.
- Check whether antivirus or endpoint security is scanning Git, Node, shell, or project files during tool calls.
- Temporarily disable nonessential MCP tools or large project context to test whether token load is the bottleneck.
- If the same task is slow through API requests too, move back to Claude API status and recent model incidents.
Claude Components That Can Feel Slow
Latency can appear on Claude.ai, Claude API, Claude Code, Console, or only in a local browser, network, account, or prompt workflow.
| Component | Status | What it affects |
|---|---|---|
| claude.ai | operational | Web app, chat UI, and login experience. |
| Claude Console (platform.claude.com) | operational | Developer console and platform settings. |
| Claude API (api.anthropic.com) | operational | API requests to api.anthropic.com. |
| Claude Code | operational | Coding agent, CLI, and IDE-related workflows. |
| Claude Cowork | operational | Team collaboration features. |
| Claude for Government | operational | Government environment. |
Recent Incidents That May Explain Slow Claude
Recent official incidents can explain slow answers, intermittent timeouts, elevated errors, or Claude Code delays even after recovery.
resolved
elevated errors on Opus 48
No component listed
Elevated errors on Opus 4.8 Fast
No component listed
Elevated error rate on Claude Opus 4.8
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated error rate across multiple models
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated errors for Claude Opus 4.8
claude.ai, Claude Console (platform.claude.com), Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated errors across many models
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated errors for Claude Opus 4.8
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, Sonnet 4.6, and Haiku 4.5
claude.ai, Claude API (api.anthropic.com), Claude Code, Claude Cowork
Claude is slow, but not fully down
When Claude still works but feels slow, separate service-side latency from local browser, network, account, prompt, or tool-specific causes.
- Check whether the slowness happens on Claude.ai, Claude API, Claude Code, or all three.
- Look for recent incidents involving the exact component you use.
- If the official status page is green, still check for model-specific incidents, usage limits, and recent recovery windows.
- Retry with a shorter prompt or smaller file upload to rule out prompt-size latency.
- Try another browser, private window, or network if only Claude.ai feels slow.
- For Claude Code terminal lag, test another shell, a fresh session, and fewer MCP tools before assuming a service outage.
- For API or Claude Code delays, compare request logs, model choice, usage limits, rate limits, and authentication state.
FAQ
Why is Claude so slow today?
Claude may be slow because of degraded service, high demand, a recent incident, model-specific latency, account limits, browser issues, network routing, or Claude Code/API problems.
Is Claude slow the same as Claude down?
No. Claude can be slow while still partially working. A full outage usually means Claude.ai, the API, or Claude Code is unavailable or returning repeated failures.
Why is Claude Code slow today?
Claude Code can be slow because of API latency, model congestion, long context windows, tool calls, CLI or IDE state, authentication, rate limits, local network issues, or a broader Claude incident.
Why does Claude status say operational when Claude is still slow?
The official status page can be green while a single model, region, account, long prompt, browser session, API route, or Claude Code workflow is still slow. Check recent incidents, component status, and whether the delay happens across web, API, and Claude Code.
Did Claude Code get slower or worse recently?
If Claude Code feels slower, first separate service latency from workflow size. Large repositories, long context, many tool calls, model changes, usage limits, and local IDE state can all feel like degradation even without a full outage.
Why is Claude getting slower?
If Claude is getting slower over several sessions, compare recent incidents with model choice, long conversations, prompt size, uploaded files, browser state, account limits, and whether Claude Code or API requests show the same slowdown.
Why does Claude take long to respond?
Claude can take long to respond when the model is under load, the prompt is large, the conversation has too much context, tools or file uploads are involved, API requests are timing out, or a recent incident is still recovering.
Can Claude usage limits feel like Claude being slow?
Yes. Usage limits, quota pressure, rate limits, or reduced model availability can make Claude Code and API workflows feel slower or less reliable even when Claude is not fully down.
Why is Claude Code slow on Windows or in my terminal?
Terminal-specific slowness can come from PowerShell, antivirus scanning, Node/runtime issues, long sessions, MCP tools, large context, or a local shell setup. Compare another terminal, a smaller project, and a fresh Claude Code session before assuming a Claude outage.
Is Claude API slow right now?
Check the Claude API component and recent incidents. API latency can affect Claude Code, developer apps, and long-running requests even when Claude.ai still appears to work.
Can Claude API be slow while Claude.ai works?
Yes. Claude.ai, Claude API, Claude Code, and Console can have separate latency or error patterns, so check the component that matches your workflow.
What should I try when Claude is slow?
Check recent incidents, retry after a short wait, test another browser or network, reduce large prompts or file uploads, and compare whether the issue appears on web, API, or Claude Code.