Report spike at 21:36 UTC — 11 reports over 13m. Most common: 'Not working' (80%); most reports from Urussanga.
No problems reported at ChatGPT right now
Problem reports for ChatGPT are at their usual level right now. The most recent incident was about 2 days ago.
reports · 24 h · /15 min
1h–15m–5m–
ChatGPT not working for you?
what people report · last 24 h
Not working100%
where from · last 24 h
no located reports in this window
outage map · last 24 h
live pulse
- social
chatgpt went down and suddenly everyone remembered how to ask a coworker3h - social
chatGPT down?6h - social
Is there a ChatGPT outage?
It's not letting me open my previous chats.
@sama11h - social
@ChatGPT Dots calling function is still NOT working for me. Anyone else have the same iss…16h - social
@crzyforhc haechan 🤤🤤🤤 but we need to get ilichils to put the chatgpt DOWN20h - social
i Dont think i can live my life if this continues. please Put the chatgpt down21h
catalogChatGPT is an OpenAI product.
ChatGPT outage record
all services by year →18 incidents in the past 12 months — 2 major, the worst on 2026-09-03 with 846 reports over 1h 30m.
Reports here usually concern not working, mostly from Romania, Sweden and Brazil.
Since 2024, down.now has recorded 46 outage days on ChatGPT, 6 of them major; the largest was Sep 3, 2026 with 846 reports, across 8 countries.
Outage — problem reports peaked at 28/15min around 23:00 UTC; 82 reports over 57m. Most common: 'Not working' (79%); reports from Indonesia and India. The company acknowledged it 19m after the first reports.
- reports
- 82
- duration
- 57m
- top problem
- Not working 79%
- most affected
- ID 50% · of 2 countries
- peak
- 28 / 15 min @ 22:45 UTC
- official ack
- +19m after reports
story · 5 beats
- 22:41 Problem reports started climbing at 22:41 UTC.
- 22:59 The company acknowledged it at 22:59 UTC — 19m after the first reports.
- 23:00 Peak at 23:00 UTC: 28/15min.
- 23:38 Problem reports faded around 23:38 UTC.
- 23:55 The company gave the all-clear at 23:55 UTC.
Major outage — problem reports peaked at 138/15min around 15:05 UTC; 846 reports over 1h 30m. Most common: 'Not working' (87%); reports from the United States, France, Spain and 5 more countries. The company acknowledged it 17m after the first reports.
- reports
- 846
- duration
- 1h 30m
- top problem
- Not working 87%
- most affected
- US 52% · of 8 countries
- peak
- 138 / 15 min @ 15:15 UTC
- official ack
- +17m after reports
Went down at the same time as Claude and Gemini.
story · 6 beats
- 14:42 Problem reports started climbing at 14:42 UTC.
- 14:58 The company acknowledged it at 14:58 UTC — 17m after the first reports.
- 15:05 Peak at 15:05 UTC: 138/15min.
- 15:45 Down to under half the peak by 15:45 UTC.
- 16:12 Problem reports faded around 16:12 UTC.
- 16:56 The company gave the all-clear at 16:56 UTC.
reports · 2026-09-03 · /15 min
incident timeline
- 14:42Problem reports started climbing.
- 14:58The company acknowledged it — 17m after the first reports.
- 15:05Peak: 138/15min.
- 15:45Down to under half the peak.
- 16:12Problem reports faded.
- 16:56The company gave the all-clear.
outage map
Outage — problem reports peaked at 33/15min around 00:10 UTC; 39 reports over 24m. Most common: 'Not working' (89%). The company acknowledged it 39m after the first reports.
- reports
- 39
- duration
- 24m
- top problem
- Not working 89%
- peak
- 33 / 15 min @ 00:00 UTC
- official ack
- +39m after reports
story · 5 beats
- 23:57 Problem reports started climbing at 23:57 UTC.
- 00:10 Peak at 00:10 UTC: 33/15min.
- 00:21 Problem reports faded around 00:21 UTC.
- 00:35 The company acknowledged it at 00:35 UTC — 39m after the first reports.
- 00:54 The company gave the all-clear at 00:54 UTC.
Major outage — problem reports peaked at 55/15min around 09:35 UTC; 483 reports over 3h 13m. Most common: 'Not working' (85%); reports from India, Japan, the United States and 20 more countries. The company acknowledged it 15m after the first reports.
- reports
- 483
- duration
- 3h 13m
- top problem
- Not working 85%
- most affected
- IN 21% · of 23 countries
- peak
- 55 / 15 min @ 09:15 UTC
- official ack
- +15m after reports
story · 6 beats
- 09:04 Problem reports started climbing at 09:04 UTC.
- 09:18 The company acknowledged it at 09:18 UTC — 15m after the first reports.
- 09:35 Peak at 09:35 UTC: 55/15min.
- 11:57 The company gave the all-clear at 11:57 UTC.
- 12:00 Down to under half the peak by 12:00 UTC.
- 12:17 Problem reports faded around 12:17 UTC.
Disruption at 18:43 UTC — 46 reports over 30m. Most common: 'Not working' (77%); reports from India, Brazil, Germany and 8 more countries.
Outage — problem reports peaked at 43/15min around 14:45 UTC; 91 reports over 35m. Most common: 'Not working' (85%); reports from Germany, France, Türkiye and 10 more countries. The company acknowledged it 28m after the first reports.
- reports
- 91
- duration
- 35m
- top problem
- Not working 85%
- most affected
- DE 18% · of 13 countries
- peak
- 43 / 15 min @ 14:45 UTC
- official ack
- +28m after reports
story · 5 beats
- 14:23 Problem reports started climbing at 14:23 UTC.
- 14:45 Peak at 14:45 UTC: 43/15min.
- 14:50 The company acknowledged it at 14:50 UTC — 28m after the first reports.
- 14:58 Problem reports faded around 14:58 UTC.
- 16:55 The company gave the all-clear at 16:55 UTC.
Disruption at 23:46 UTC — 62 reports over 33m. Most common: 'Not working' (83%); reports from Nicaragua, the United States, Malaysia and 1 more country.
Report spike at 17:02 UTC — 12 reports over 22m.
Disruption at 03:03 UTC — 18 reports over 21m.
Disruption at 14:23 UTC — 91 reports over 1h 25m. Most common: 'Not working' (46%); reports from Spain, the United Kingdom, Costa Rica and 8 more countries.
Incident at 17:17 UTC — 52 reports over 37m.
Incident at 20:18 UTC — 284 reports over 1h 32m.
Incident at 19:30 UTC — 159 reports over 44m.
Incident at 12:12 UTC — 307 reports over 7h 8m.
During the Cloudflare outage.
Incident at 07:18 UTC — scattered reports over 2h 20m.
Incident at 16:32 UTC — scattered reports over 32m.
Incident at 01:23 UTC — scattered reports over 2h 10m.
Incident at 01:09 UTC — scattered reports over 17m.
Incident at 19:03 UTC — scattered reports over 15m.
Major outage — problem reports stayed above normal, lasting 10h 47m.
- duration
- 10h 47m
Incident at 21:46 UTC — scattered reports over 20m.
Incident at 10:55 UTC — scattered reports over 23m.
Incident at 19:41 UTC — scattered reports over 17m.
Major outage — problem reports stayed above normal, lasting 3h 25m.
- duration
- 3h 25m
Incident at 20:14 UTC — scattered reports over 1h 38m.
Major outage — problem reports stayed above normal, lasting 5h 8m.
- duration
- 5h 8m
Incident at 00:27 UTC — scattered reports over 29m.
Incident at 00:09 UTC — scattered reports over 46m.
Incident at 16:40 UTC — scattered reports over 1h 24m.
Incident at 15:45 UTC — scattered reports over 1h 8m.
Major outage — problem reports stayed above normal, lasting 4h 5m.
- duration
- 4h 5m
Incident at 13:51 UTC — scattered reports over 1h 35m.
Incident at 01:19 UTC — 25 reports over 20m.
Incident at 21:54 UTC — 116 reports over 1h 10m.
ChatGPT comments
anonymous · no accountcommon questions
Is ChatGPT down right now?
Problem reports for ChatGPT are at their usual level right now. The most recent incident was about 2 days ago.
Is ChatGPT down for everyone or just me?
Right now down.now isn't seeing a broad ChatGPT 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 ChatGPT last go down?
The last recorded ChatGPT incident was about 2 days ago, on 2026-09-30. The outage record below has the peak time, duration and what people reported.
How can I report a problem with ChatGPT?
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 ChatGPT is down?
Down.Now watches two crowd signals for ChatGPT — 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 ChatGPT's servers directly.