Outage — problem reports peaked at 47/15min around 14:30 UTC; 133 reports over 58m. Most common: 'Not working' (65%); reports from the United States, the United Kingdom, Portugal and 3 more countries.
reports
133
duration
58m
top problem
Not working 65%
most affected
US 62% · of 6 countries
peak
47 / 15 min @ 14:30 UTC
story · 4 beats
14:11 ↗ Problem reports started climbing at 14:11 UTC.
Disruption at 00:53 UTC — 22 reports over 24m. Most common: 'Not working' (57%); most reports from San Francisco.
2026-09-03 Major outage 3h 39m · 512 signals ▶ view this daychart · map · replay
Major outage — problem reports peaked at 76/15min around 15:05 UTC; 512 reports over 3h 39m. Most common: 'Not working' (76%); reports from the United States, Pakistan, Australia and 7 more countries. The company acknowledged it 7m after the first reports.
Outage — problem reports peaked at 31/15min around 22:00 UTC; 86 reports over 38m. Most common: 'Not working' (58%); reports from the United States, Israel, Türkiye and 6 more countries.
reports
86
duration
38m
top problem
Not working 58%
most affected
US 18% · of 9 countries
peak
31 / 15 min @ 22:00 UTC
story · 3 beats
21:49 ↗ Problem reports started climbing at 21:49 UTC.
Outage — problem reports peaked at 42/15min around 20:05 UTC; 179 reports over 2h 1m. Most common: 'Not working' (64%); reports from the United States, Canada, Brazil and 3 more countries. The company acknowledged it 3m after the first reports.
reports
179
duration
2h 1m
top problem
Not working 64%
most affected
US 29% · of 6 countries
peak
42 / 15 min @ 20:00 UTC
official ack
+3m after reports
story · 5 beats
19:52 ↗ Problem reports started climbing at 19:52 UTC.
19:54 ⚑ The company acknowledged it at 19:54 UTC — 3m after the first reports.
Outage — problem reports peaked at 31/15min; 123 reports over 1h 29m. Most common: 'Servers / connection' (25%); reports from Vietnam, Belgium, Bulgaria and 1 more country.
Disruption at 00:36 UTC — 24 reports over 33m. Most common: 'Servers / connection' (38%); reports from Brazil, the United States, Japan and 5 more countries.
Disruption at 07:00 UTC — 48 reports over 45m. Most common: 'Servers / connection' (40%); reports from Greece, India, the Philippines and 1 more country.
Problem reports for Claude are at their usual level right now. The most recent incident was about 4 days ago.
Is Claude down for everyone or just me?
Right now down.now isn't seeing a broad Claude outage, so the problem is most likely local to you — your connection, your device, or the app itself. Try the app on mobile data instead of Wi-Fi, then restart the router. If reports start arriving from other people, this page flips to an outage within minutes.
When did Claude last go down?
The last recorded Claude incident was about 4 days ago, on 2026-09-29. The outage record below has the peak time, duration and what people reported.
How can I report a problem with Claude?
Use the report panel on this page and pick what's not working — it takes one tap and no account. Reports are anonymous, and they feed the live signal on this page immediately.
How does down.now know if Claude is down?
Down.Now watches two crowd signals for Claude — anonymous reports submitted here, and public social-media posts about it — and compares the live volume against what's normal for that hour of the day. A sustained spike above that baseline opens an incident, which is usually visible before an official confirmation. We measure what users report, not Claude's servers directly.
@bridgemindai @bridgebench I knew something shady when Claude services down for 3h.
Cant tell if there's a claude outage, or my internet is spotty or both