OpenAI logo

ChatGPT API disruption on 18 November 2026

ChatGPT API from Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal: degraded checks; 2026-11-18 08:00 UTC to 2026-11-18 13:30 UTC: peak first visible token 3.03 s vs a usual 1.11 s.

What our checks saw
Degraded
Cities affected
Amsterdam, Mumbai, San Francisco, Singapore, Tokyo, Montreal
When
to
How long
5.5 hours
Slowest check
3.03 s, usually 1.11 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 s05:0008:0011:0014:00
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
05:001.01 sNormal
05:301.22 sNormal
06:00708 msNormal
06:30835 msNormal
07:00881 msNormal
07:301.03 sNormal
08:003.54 sMuch slower, or failing
08:302.52 sSlower than usual
09:002.43 sSlower than usual
09:302.01 sSlower than usual
10:001.52 sNormal
10:301.79 sSlower than usual
11:001.14 sNormal
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

San Francisco

Incident0 ms2.00 s4.00 s05:0008:0011:0014:00
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
05:001.44 sNormal
05:30963 msNormal
06:001.36 sNormal
06:30740 msNormal
07:001.32 sNormal
07:30–No check
08:00–No check
08:302.34 sNo check
09:002.77 sMuch slower, or failing
09:302.00 sSlower than usual
10:00733 msNormal
10:30724 msNormal
11:00670 msNormal
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

Montreal

Incident0 ms2.00 s4.00 s05:0008:0011:0014:00
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
05:00846 msNormal
05:301.22 sNormal
06:00851 msNormal
06:301.02 sNormal
07:001.16 sNormal
07:301.75 sSlower than usual
08:003.53 sMuch slower, or failing
08:302.01 sSlower than usual
09:002.51 sSlower than usual
09:301.65 sSlower than usual
10:00918 msNormal
10:301.59 sSlower than usual
11:00998 msNormal
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

Singapore

Incident0 ms2.50 s5.00 s05:0008:0011:0014:00
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
05:001.30 sNormal
05:301.09 sNormal
06:001.27 sNormal
06:301.39 sNormal
07:001.24 sNormal
07:301.01 sNormal
08:003.02 sMuch slower, or failing
08:302.09 sSlower than usual
09:002.25 sSlower than usual
09:302.14 sSlower than usual
10:001.35 sNormal
10:30964 msNormal
11:001.38 sNormal
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

Tokyo

Incident0 ms2.00 s4.00 s05:0008:0011:0014:00
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
05:001.18 sNormal
05:30983 msNormal
06:001.64 sNormal
06:301.35 sNormal
07:00809 msNormal
07:301.53 sNormal
08:003.44 sMuch slower, or failing
08:302.62 sSlower than usual
09:002.76 sSlower than usual
09:302.69 sSlower than usual
10:001.23 sNormal
10:301.56 sNormal
11:001.10 sNormal
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

Mumbai

Incident0 ms2.00 s4.00 s05:0008:0011:0014:00
Each check (UTC)Usual (1.31 s)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
05:001.08 sNormal
05:301.23 sNormal
06:001.28 sNormal
06:301.23 sNormal
07:001.00 sNormal
07:301.46 sNormal
08:002.73 sSlower than usual
08:302.20 sSlower than usual
09:002.72 sSlower than usual
09:302.27 sSlower than usual
10:001.04 sNormal
10:301.53 sNormal
11:001.26 sNormal
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

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.