GitHub outage — July 16, 2026

Disruption with GPT 5.3 Codex

GitHub’s Multiple services was disrupted for 4d 15h on July 16, 2026. 503Radar’s sensors raised the first signal at 02:43 UTC, 6h 34m before the official status page acknowledged impact.

Key facts

Timeline

1. 02:43Z

   Detected · Signal

   11 crowd signals for Multiple services on GITHUB crossed the signal threshold.
2. 09:18Z

   Confirmed · Official

   An official GITHUB status-page notice corroborated the event — 6h 34m after detection.
3. 18:34Z

   Resolved

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

What people reported

“Though my nostr-mastodon (nostrdon) bridge seems down (and I simply cannot get mostr to work), that's ok. It's OK because my nostr-hive bridge (hostr) is workin”bluesky_jetstream · 08:24 UTC

“N/BOT Is going to be fully shut down since I left the server it was made for, It is complete with many different "Modules" Which most of them are very good, So ”bluesky_jetstream · 09:20 UTC

“📦 bugboard/sdk 1.1.0 Official BugBoard SDK for PHP — report errors as cards on your project board, with first-class Laravel and Symfony support. 🔗 https://git”bluesky_jetstream · 10:05 UTC

“Having trouble using transcription tools like FLEx and ELAN? I've created a browser-based, lightweight, and (probably) much more intuitive transcription tool f”bluesky_jetstream · 10:42 UTC

“PS4 News: The spoofer has been taken down since it was broken due AI. It has now been reworked and the AI vibecodes have been removed by an actual dev. Same ”bluesky_jetstream · 11:12 UTC

“Also fixed: a cross-request session ID leak in worker mode when the session extension is a shared module. And slow-POST protection is now on by default, a 60s ”bluesky_jetstream · 12:50 UTC

How this was detected

1 independent evidence class for Multiple services on GITHUB. 11 crowd reports across bluesky (single platform — not corroborating), z=-0.5σ vs the cell baseline. Official notice confirms it, 6h 34m after the crowd.