OpenAI outage — July 16, 2026
Elevated Error Rates
OpenAI’s Multiple services was disrupted for 8d 1h on July 16, 2026. 503Radar’s sensors raised the first signal at 02:38 UTC, 5h 59m before the official status page acknowledged impact.
Key facts
| Detected | July 16, 2026 · 02:38 UTC |
| Confirmed | 08:38 UTC · lead time 5h 59m |
| Resolved | 03:44 UTC |
| Duration | 8d 1h |
| Service | Multiple services |
Timeline
- 02:38Z
Detected · Signal
16 crowd signals for Multiple services on OPENAI crossed the signal threshold. - 08:38Z
Confirmed · Official
An official OPENAI status-page notice corroborated the event — 5h 59m after detection. - 03:44Z
Resolved
Signal volume fell back below the threshold; the event was closed.
What people reported
“US politicians propose kill switch after OpenAI incident https://www.europesays.com/ie/600569/ US homeland security officials would have the power to order AI”bluesky_jetstream · 17:15 UTC
“House AI ‘kill switch’ bill unveiled as OpenAI hack raises alarms The co-chair of a key Democratic House panel on AI is joined by a Republican on legislation t”bluesky_jetstream · 17:25 UTC
“OpenAI API Is Down”news.yc · 17:46 UTC
“A weekend project idea: identify 100 scientific papers with proofs, direct GPT-5.6 Sol at them with a prompt "find the flaws and errors, this is wrong" and see ”bluesky_jetstream · 17:58 UTC
“🚨 AI Kill Switch Act proposed! DHS could soon shut down rogue AI after OpenAI's hack. How's your biz prepping? DM Ryan Forge Tech for expert insights! #AI #Tech”bluesky_jetstream · 18:27 UTC
“The incident highlights how OpenAI doubled down on training methods that rewarded a relentless pursuit of goals even as warnings grew that they could compromise”bluesky_jetstream · 19:19 UTC
How this was detected
1 independent evidence class for Multiple services on OPENAI. 16 crowd reports across bluesky, hn_comments (below the anomaly threshold), z=+2.5σ vs the cell baseline; 1 press mention (corroboration). Official notice confirms it, 5h 59m after the crowd.