OpenAI Decisions API disruption on 12 October 2026
OpenAI Decisions API full response from Mumbai, Singapore, Tokyo: degraded checks; 2026-10-12 01:30 UTC to 2026-10-12 04:30 UTC: peak full response 2.53 s vs a usual 303 ms.
- What our checks saw
- Degraded
- Cities affected
- Mumbai, Singapore, Tokyo
- When
- to
- How long
- 3 hours
- Slowest check
- 2.53 s, usually 303 ms
- 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.
Singapore
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 22:30 | 346 ms | Normal |
| 23:00 | 422 ms | Normal |
| 23:30 | 373 ms | Normal |
| 00:00 | 342 ms | Normal |
| 00:30 | 856 ms | Much slower, or failing |
| 01:00 | 416 ms | Normal |
| 01:30 | 523 ms | Slower than usual |
| 02:00 | 300 ms | Normal |
| 02:30 | 4.66 s | Much slower, or failing |
| 03:00 | 401 ms | Normal |
| 03:30 | 288 ms | Normal |
| 04:00 | 410 ms | Normal |
| 04:30 | 282 ms | Normal |
| 05:00 | 663 ms | Slower than usual |
| 05:30 | 282 ms | Normal |
| 06:00 | 280 ms | Normal |
| 06:30 | 279 ms | Normal |
| 07:00 | 299 ms | Normal |
| 07:30 | 340 ms | Normal |
Tokyo
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 22:30 | 218 ms | Normal |
| 23:00 | 359 ms | Normal |
| 23:30 | 187 ms | Normal |
| 00:00 | 215 ms | Normal |
| 00:30 | 211 ms | Normal |
| 01:00 | 466 ms | Slower than usual |
| 01:30 | 409 ms | Normal |
| 02:00 | 316 ms | Normal |
| 02:30 | 4.14 s | Much slower, or failing |
| 03:00 | 202 ms | Normal |
| 03:30 | 220 ms | Normal |
| 04:00 | 213 ms | Normal |
| 04:30 | 196 ms | Normal |
| 05:00 | 201 ms | Normal |
| 05:30 | 202 ms | Normal |
| 06:00 | 320 ms | Normal |
| 06:30 | 198 ms | Normal |
| 07:00 | 203 ms | Normal |
| 07:30 | 204 ms | Normal |
Mumbai
Every check as a table
| Time (UTC) | Check | Reading |
|---|---|---|
| 22:30 | 319 ms | Normal |
| 23:00 | 104 ms | Normal |
| 23:30 | 1.18 s | Much slower, or failing |
| 00:00 | 158 ms | Normal |
| 00:30 | 128 ms | Normal |
| 01:00 | 220 ms | Normal |
| 01:30 | 1.22 s | Much slower, or failing |
| 02:00 | 149 ms | Normal |
| 02:30 | 3.88 s | Much slower, or failing |
| 03:00 | 120 ms | Normal |
| 03:30 | 193 ms | Normal |
| 04:00 | 356 ms | Slower than usual |
| 04:30 | 116 ms | Normal |
| 05:00 | 108 ms | Normal |
| 05:30 | 365 ms | Slower than usual |
| 06:00 | 319 ms | Slower than usual |
| 06:30 | 210 ms | Our check could not be verified |
| 07:00 | 1.06 s | Much slower, or failing |
| 07:30 | 471 ms | Much slower, or failing |
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.
No account required · Takes about 30 seconds.