GitHub outage — July 16, 2026
Disruption with some GitHub services
GitHub’s Multiple services was disrupted for 6h 56m 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
| Detected | July 16, 2026 · 02:43 UTC |
| Confirmed | 09:18 UTC · lead time 6h 34m |
| Resolved | 09:39 UTC |
| Duration | 6h 56m |
| Service | Multiple services |
| Official record | https://stspg.io/5c43kg01skdw |
Timeline
- 02:43Z
Detected · Signal
3 crowd signals for Multiple services on GITHUB crossed the signal threshold. - 09:18Z
Confirmed · Official
An official GITHUB status-page notice corroborated the event — 6h 34m after detection. - 09:39Z
Resolved
Signal volume fell back below the threshold; the event was closed.
What people reported
“OpenCode now supports Lynkr through models.dev. Use local models for cheap requests and stronger APIs for hard ones, with evidence-based auto-escalation so ses”bluesky_jetstream · 23:06 UTC
“Has been a fun week of events here in Berlin 🎉 Now got a couple of days to wind down before I leave (and catch up on GitHub 😅)”bluesky_jetstream · 06:35 UTC
“📦 blutrixx/generator-engine 2.10.1 Module code generator engine for Laravel + Vue 3 + NativePHP Mobile. Generates backend modules, frontend pages, mobile backe”bluesky_jetstream · 07:37 UTC
How this was detected
1 independent evidence class for Multiple services on GITHUB. 3 crowd reports across bluesky (single platform — not corroborating), z=-0.4σ vs the cell baseline. Official notice confirms it, 6h 34m after the crowd.