OpenAI logo

ChatGPT API slowdown on 9 November 2026

ChatGPT API from Singapore: slower than usual; 2026-11-09 02:30 UTC to 2026-11-09 04:00 UTC: peak first visible token 2.24 s vs a usual 1.22 s.

What our checks saw
Slower than usual
Cities affected
Singapore
When
to
How long
90 minutes
Slowest check
2.24 s, usually 1.22 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. Not affected: Amsterdam, San Francisco, Montreal, Tokyo, Mumbai.

Singapore

Incident0 ms1.50 s3.00 s23:3002:3005:30
Each check (UTC)Usual (1.22 s)Slower than usualSlow check outside the incidentIncident
Every check as a table
Time (UTC)CheckReading
23:301.32 sNormal
00:001.41 sNormal
00:301.05 sNormal
01:001.46 sNormal
01:302.24 sSlower than usual
02:002.18 sSlower than usual
02:302.30 sSlower than usual
03:00995 msNormal
03:301.09 sNormal
04:001.49 sNormal
04:30919 msNormal
05:001.11 sNormal
05:301.42 sNormal
06:001.10 sNormal
06:301.21 sNormal
07:001.06 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.