Claude Status
Official status dashboard for Claude services.
Live Domain Check
Check if Claude is down right now (claude.ai). Run a live multi-region check to see whether Claude is offline for everyone or just you.
Get official Claude outage status updates, support links, and targeted troubleshooting steps in one page.
Checking reachability from multiple regions.
Claude incidents can impact web access, specific models, API connectivity, or desktop workflows independently. Component-level checks are essential for accurate root-cause triage.
For Claude, incident signals are often feature-specific: Web UI loads but model requests fail intermittently. API errors increase while consumer UI remains partly available. If this matches what you see on claude.ai, it usually points to partial degradation instead of a full outage, so confirm with official status updates and a second-network retest.
Claude has an official status page with component health for claude.ai, platform, and API endpoints.
Official status dashboard for Claude services.
Official troubleshooting and support entry point.
Official API and platform technical documentation.
Monitor real-time social updates and official posts related to Claude outages.
Official teams often post outage status updates and recovery progress through these social channels.
Use these service-specific patterns to identify likely root cause quickly and choose the right next step.
Practical steps to follow when claude.ai seems down. Use this checklist to confirm whether Claude is down for everyone or only for you.
Run claude.ai in WebsiteDown.org first, then open claude.ai in your own browser. If results disagree, the issue is often local rather than global.
Check the official Claude service status page and compare timestamps with your failed checks.
Test related hosts such as status.claude.com, support.anthropic.com. If they work while claude.ai fails, this points to a partial endpoint issue.
Capture final URL, status code, and response time for claude.ai, then share those details with Claude support for faster triage and recovery.
Use these local troubleshooting steps after the down-check workflow when Claude seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open claude.ai in your current browser, then test in a private window or second browser. If only one session fails, the issue is usually local cache, cookie, or extension state.
Sign out and sign back in one time, then retry the failing action on claude.ai. Avoid repeated password or security resets until you confirm this is not a broader Claude issue.
Temporarily disable VPN, proxy, private DNS, and filtering extensions. Then switch between Wi-Fi and mobile data to isolate route-level differences.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Claude support.
Run the automatic multi-region check on this page for claude.ai. If most regions fail at the same time, Claude is likely experiencing a broader outage or partial incident.
If only one or two regions fail, the issue is usually local to your network path (DNS resolver, ISP route, VPN/proxy, or firewall). Re-check after 2 to 5 minutes and compare Wi-Fi with mobile data.
Use the Official Status, Support, and Social Channels section above in this order:
Official dashboards are authoritative but can lag during the first minutes of an incident. Combine those sources with this checker to confirm whether Claude is down globally, regionally degraded, or only affecting specific users.
That pattern usually points to path-specific issues rather than a full Claude outage. Common causes include:
Test in a private window, temporarily disable VPN/extensions, and retry from a second network. If one feature fails while the homepage still loads, treat it as a partial incident.
Use this quick triage sequence for claude.ai:
This order helps you avoid unnecessary account resets when the Claude issue is provider-side.