OpenAI logo

ChatGPT API disruption on 5 October 2026

ChatGPT API from Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal: degraded checks; 2026-10-05 19:30 UTC to 2026-10-05 21:30 UTC: peak first visible token 3.22 s vs a usual 1.2 s.

What our checks saw
Degraded
Cities affected
Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
When
to
How long
2 hours
Slowest check
3.22 s, usually 1.20 s
OpenAI's status page
Open it

Where our checks saw it

Each glowing city had slow or failing checks during the incident, shown at its worst. We test from 6 cities, so other places may have been hit too.

Our checks, city by city

Each point is one check every 30 minutes, from three hours before the incident to three hours after. Coloured points are the checks we counted as slower or failing. The shaded area shows how far above the usual time they were.

Amsterdam

Incident0 ms2.00 s4.00 s16:3019:3022:30
Each check (UTC)Usual (1.18 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
16:301.51 sNormal
17:001.27 sNormal
17:301.27 sNormal
18:001.38 sNormal
18:301.76 sNormal
19:001.78 sSlower than usual
19:303.35 sMuch slower, or failing
20:001.58 sNormal
20:301.36 sNormal
21:001.36 sNormal
21:301.29 sNormal
22:001.30 sNormal
22:301.43 sNormal
23:001.12 sNormal
23:301.09 sNormal
00:001.39 sNormal
00:301.50 sNormal

San Francisco

Incident0 ms2.50 s5.00 s16:3019:3022:30
Each check (UTC)Usual (1.10 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
16:301.56 sNormal
17:001.06 sNormal
17:301.08 sNormal
18:001.08 sNormal
18:301.63 sNormal
19:001.95 sSlower than usual
19:304.03 sMuch slower, or failing
20:001.63 sNormal
20:301.45 sNormal
21:001.24 sNormal
21:30849 msNormal
22:001.03 sNormal
22:30888 msNormal
23:001.51 sNormal
23:30896 msNormal
00:001.06 sNormal
00:301.85 sSlower than usual

Montreal

Incident0 ms2.50 s5.00 s16:3019:3022:30
Each check (UTC)Usual (1.13 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
16:301.03 sNormal
17:00903 msNormal
17:30776 msNormal
18:001.97 sSlower than usual
18:301.42 sNormal
19:001.50 sNormal
19:303.97 sMuch slower, or failing
20:001.14 sNormal
20:301.35 sNormal
21:00957 msNormal
21:301.11 sNormal
22:001.49 sNormal
22:30843 msNormal
23:001.45 sNormal
23:301.16 sNormal
00:001.54 sNormal
00:302.65 sSlower than usual

Singapore

Incident0 ms2.50 s5.00 s16:3019:3022:30
Each check (UTC)Usual (1.20 s)Slower than usualMuch slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
16:301.71 sNormal
17:001.60 sNormal
17:301.35 sNormal
18:001.68 sNormal
18:301.78 sNormal
19:001.47 sNormal
19:304.46 sMuch slower, or failing
20:001.16 sNormal
20:302.09 sSlower than usual
21:001.17 sNormal
21:301.11 sNormal
22:001.12 sNormal
22:301.94 sSlower than usual
23:001.16 sNormal
23:301.03 sNormal
00:001.49 sNormal
00:301.21 sNormal

Tokyo

Incident0 ms2.50 s5.00 s16:3019:3022:30
Each check (UTC)Usual (1.20 s)Much slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
16:301.48 sNormal
17:001.94 sSlower than usual
17:301.50 sNormal
18:001.59 sNormal
18:301.39 sNormal
19:002.04 sSlower than usual
19:304.41 sMuch slower, or failing
20:001.32 sNormal
20:301.22 sNormal
21:001.62 sNormal
21:301.06 sNormal
22:001.28 sNormal
22:301.15 sNormal
23:001.56 sNormal
23:301.16 sNormal
00:001.89 sSlower than usual
00:30995 msNormal

Mumbai

Incident0 ms2.50 s5.00 s16:3019:3022:30
Each check (UTC)Usual (1.56 s)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
16:301.53 sNormal
17:001.67 sNormal
17:301.39 sNormal
18:001.99 sNormal
18:301.20 sNormal
19:002.33 sNormal
19:303.79 sSlower than usual
20:001.55 sNormal
20:302.41 sSlower than usual
21:002.07 sNormal
21:301.54 sNormal
22:001.52 sNormal
22:301.97 sNormal
23:002.42 sSlower than usual
23:301.86 sNormal
00:002.05 sNormal
00:301.53 sNormal

How fast is your API around the world?

Run a free speed test from multiple cities and find out where your users are waiting. No setup, no account required.

Test my API

No account required · Takes about 30 seconds.