GitHub outage — July 16, 2026

Several GPT models degraded

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

   14 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. 10:14Z

   Resolved

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

What people reported

“Hello ALL, does anyone know why OpenScreen's repository on GitHub is now read only? The original website is offline. https://github.com/siddharthvaddem/opensc”bluesky_jetstream · 22:56 UTC

“RT @Wraient: > - Fixed Android VPN and Tailscale connections showing as offline Spend my week working on this PR https://github.com/pingdotgg/t3code/pull/3949”bluesky_jetstream · 23:07 UTC

“📦 asmaa-gamal/laravel-meta-messaging v1.0.0 Send Facebook Messenger and Instagram messages from Laravel — every message type, with pre-flight validation and cl”bluesky_jetstream · 02:54 UTC

“India ordering GitHub to take down Bitchat—a mesh app that routes encrypted messages over Bluetooth—drew heavy pushback on HN. The sharpest complaint was that b”bluesky_jetstream · 03:00 UTC

“@phocks GitHub went down in the US for ReadTheDocs and Xed-Editor CI pipelines.”bluesky_jetstream · 03:25 UTC

“📦 asmaa-gamal/laravel-meta-messaging v1.0.1 Send Facebook Messenger and Instagram messages from Laravel — every message type, with pre-flight validation and cl”bluesky_jetstream · 04:01 UTC

How this was detected

2 independent evidence classes for Multiple services on GITHUB. 15 crowd reports across bluesky (independent class), z=+3.6σ vs the cell baseline. Official notice confirms it, 6h 34m after the crowd.