OpenAI logo

ChatGPT API disruption on 18 November 2026

ChatGPT API from Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal: degraded checks; 2026-11-18 14:30 UTC to 2026-11-18 19:30 UTC: peak first visible token 3.28 s vs a usual 1.14 s.

What our checks saw
Degraded
Cities affected
Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
When
to
How long
5 hours
Slowest check
3.28 s, usually 1.14 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 s11:3014:3017:3020:30
Each check (UTC)Usual (1.06 s)Slower than usualMuch slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
11:301.53 sNormal
12:001.90 sSlower than usual
12:301.27 sNormal
13:001.66 sSlower than usual
13:301.00 sNormal
14:001.41 sNormal
14:303.12 sMuch slower, or failing
15:002.78 sMuch slower, or failing
15:302.63 sSlower than usual
16:002.63 sSlower than usual
16:301.79 sSlower than usual
17:001.29 sNormal
17:301.01 sNormal
18:001.35 sNormal
18:301.03 sNormal
19:001.58 sNormal
19:301.22 sNormal
20:001.09 sNormal
20:301.09 sNormal
21:00941 msNormal
21:30736 msNormal
22:001.29 sNormal
22:30943 msNormal

San Francisco

Incident0 ms2.00 s4.00 s11:3014:3017:3020:30
Each check (UTC)Usual (1.03 s)Slower than usualMuch slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
11:301.24 sNormal
12:001.27 sNormal
12:301.30 sNormal
13:00992 msNormal
13:301.28 sNormal
14:001.91 sSlower than usual
14:302.48 sSlower than usual
15:001.67 sSlower than usual
15:303.59 sMuch slower, or failing
16:002.12 sSlower than usual
16:301.45 sNormal
17:001.56 sSlower than usual
17:301.48 sNormal
18:001.89 sSlower than usual
18:30880 msNormal
19:001.47 sNormal
19:301.53 sNormal
20:001.18 sNormal
20:301.51 sNormal
21:001.42 sNormal
21:301.29 sNormal
22:001.74 sSlower than usual
22:301.68 sSlower than usual

Montreal

Incident0 ms2.00 s4.00 s11:3014:3017:3020:30
Each check (UTC)Usual (1.02 s)Slower than usualMuch slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
11:301.04 sNormal
12:001.10 sNormal
12:30957 msNormal
13:001.00 sNormal
13:30891 msNormal
14:001.76 sSlower than usual
14:302.89 sMuch slower, or failing
15:002.03 sSlower than usual
15:302.47 sSlower than usual
16:002.26 sSlower than usual
16:30940 msNormal
17:00931 msNormal
17:30898 msNormal
18:00901 msNormal
18:301.67 sSlower than usual
19:001.75 sSlower than usual
19:301.10 sNormal
20:001.28 sNormal
20:30993 msNormal
21:001.28 sNormal
21:30926 msNormal
22:001.76 sSlower than usual
22:301.02 sNormal

Singapore

Incident0 ms2.50 s5.00 s11:3014:3017:3020:30
Each check (UTC)Usual (1.14 s)Slower than usualMuch slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
11:301.08 sNormal
12:001.76 sSlower than usual
12:301.28 sNormal
13:001.30 sNormal
13:30993 msNormal
14:001.54 sNormal
14:303.94 sMuch slower, or failing
15:002.62 sSlower than usual
15:302.37 sSlower than usual
16:001.92 sSlower than usual
16:302.03 sSlower than usual
17:001.37 sNormal
17:301.05 sNormal
18:001.15 sNormal
18:301.07 sNormal
19:001.21 sNormal
19:301.42 sNormal
20:001.93 sSlower than usual
20:301.47 sNormal
21:001.45 sNormal
21:301.02 sNormal
22:001.31 sNormal
22:301.24 sNormal

Tokyo

Incident0 ms2.00 s4.00 s11:3014:3017:3020:30
Each check (UTC)Usual (1.11 s)Slower than usualMuch slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
11:301.15 sNormal
12:001.48 sNormal
12:30789 msNormal
13:001.60 sNormal
13:301.50 sNormal
14:00768 msNormal
14:303.51 sMuch slower, or failing
15:002.27 sSlower than usual
15:302.37 sSlower than usual
16:002.23 sSlower than usual
16:301.82 sSlower than usual
17:001.24 sNormal
17:30923 msNormal
18:001.73 sSlower than usual
18:301.43 sNormal
19:001.62 sNormal
19:301.11 sNormal
20:002.00 sSlower than usual
20:301.55 sNormal
21:001.15 sNormal
21:30969 msNormal
22:001.61 sNormal
22:301.13 sNormal

Mumbai

Incident0 ms2.00 s4.00 s11:3014:3017:3020:30
Each check (UTC)Usual (1.31 s)Slower than usualMuch slower, or failingSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
11:301.58 sNormal
12:001.52 sNormal
12:301.43 sNormal
13:001.31 sNormal
13:301.13 sNormal
14:001.55 sNormal
14:303.53 sMuch slower, or failing
15:002.65 sSlower than usual
15:302.66 sSlower than usual
16:002.52 sSlower than usual
16:301.36 sNormal
17:001.81 sNormal
17:301.87 sNormal
18:001.42 sNormal
18:301.35 sNormal
19:001.24 sNormal
19:301.16 sNormal
20:001.99 sSlower than usual
20:301.64 sNormal
21:001.60 sNormal
21:301.82 sNormal
22:001.67 sNormal
22:301.45 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.