GitHub outage — July 24, 2026
Incident with Pull Requests
GitHub’s Issues & PRs was disrupted for 8h 26m on July 24, 2026. 503Radar’s sensors raised the first signal at 11:43 UTC, 7h 54m before the official status page acknowledged impact.
Key facts
| Detected | July 24, 2026 · 11:43 UTC |
| Confirmed | 19:38 UTC · lead time 7h 54m |
| Resolved | 20:09 UTC |
| Duration | 8h 26m |
| Service | Issues & PRs |
| Official record | https://stspg.io/sm1tp7kfm4vj |
Timeline
- 11:43Z
Detected · Signal
3 crowd signals for Issues & PRs on GITHUB crossed the signal threshold. - 19:38Z
Confirmed · Official
An official GITHUB status-page notice corroborated the event — 7h 54m after detection. - 20:09Z
Resolved
Signal volume fell back below the threshold; the event was closed.
What people reported
“Sráči ze Stravy zavřeli API a už jen pro platící. Takže plot téhle walled garden je ještě o dva metry vyšší, než býval. Jediné zbývající backdoory jsou scrapov”bluesky_jetstream · 11:42 UTC
“Disruption with some GitHub services - Update Pull Requests is experiencing degraded performance. We are continuing to investigate. #yjysg0xrl67m”bluesky_jetstream · 16:21 UTC
“CRAN checks badges service is partially not working right now - at least the posit controlled mirrors are now throttling requests so finding a work-around # rst”#mastodon · 18:35 UTC
How this was detected
1 independent evidence class for issues-prs on GITHUB. 3 crowd reports across bluesky, mastodon (below the anomaly threshold), z=+0.5σ vs the cell baseline. Official notice confirms it, 7h 54m after the crowd.