OpenAI outage — July 16, 2026

Elevated error rates

OpenAI’s Multiple services was disrupted for 9d 9h 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

Timeline

1. 02:38Z

   Detected · Signal

   16 crowd signals for Multiple services on OPENAI crossed the signal threshold.
2. 08:38Z

   Confirmed · Official

   An official OPENAI status-page notice corroborated the event — 5h 59m after detection.
3. 12:04Z

   Resolved

   Signal volume fell back below the threshold; the event was closed.

What people reported

“Interesting that Microsoft did sign — have they already written down their OpenAI investment?”bluesky_jetstream · 00:14 UTC

“I've seen speculation, but no hard evidence. Do you have any? I'd argue that it's rather absurd to assume that just because OpenAI is operating in the red that ”bluesky_jetstream · 00:39 UTC

“i’m not gonna lie to you, of all the shit that’s gone down this week with openai, this is the thing that scares the absolute shit out of me”bluesky_jetstream · 01:27 UTC

“Several commenters argued OpenAI wants stories like this in the headlines to justify regulatory barriers against open-weight models. The theory: if AI is framed”bluesky_jetstream · 02:00 UTC

“ppl are not going to understand what happened, bc you are not explaining what the software is doing and why. it's "making decisions?" how? what does that mean? ”bluesky_jetstream · 03:19 UTC

“Whether OpenAI prioritizes reclaiming the leaderboard or doubles down on product differentiation through features like voice and vision will signal its strategi”bluesky_jetstream · 08:08 UTC

How this was detected

2 independent evidence classes for Multiple services on OPENAI. 14 crowd reports across bluesky (independent class), z=+3.3σ vs the cell baseline; 2 press mentions (corroboration). Official notice confirms it, 5h 59m after the crowd.