GitHub outage — July 16, 2026

Some SSH connections using deploy keys are failing

GitHub’s Multiple services was disrupted for 5d 8h 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. 11:14Z

   Resolved

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

What people reported

“... ... ... Nah, I'm good. You can keep it, Github. Maybe shut down a data center instead? :D”@sam-animeherald.bsky.social · 00:05 UTC

“You could probably fry what's left of my brain cells by sitting me down in front of a page on GitHub and telling me to simply try to logic out the instructions ”@wayneisboss.bsky.social · 04:43 UTC

“RAMP: Robust Ad Recommendation Under Limited Personalized-Feature Availability via Masking and Alignment Pathways Huawei presents a framework that improves CTR”bluesky_jetstream · 05:56 UTC

“A rounding error for GitHub/Microsoft. Any serious outage costs more.”@fry69.dev · 06:22 UTC

“📦 ozankurt/laravel-modules-licensing v1.0.0 Self-hosted software licensing for Laravel: issue/validate license keys, Ed25519 signed offline keys, seat activati”bluesky_jetstream · 07:44 UTC

“Koin Compiler Plugin 1.0.2 🚀 Multi-module & KMP correctness fixes: • fewer false cross-module "missing dependency" errors (#51) • iOS/Native/WASM-JS KLIB dupli”bluesky_jetstream · 08:00 UTC

How this was detected

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