← Back to the carnage
GITHUB
🟠 Pull requests decided to move at geological timescales—3% of merges hit the timeout wall. GitHub applied the digital equivalent of smacking it on the side, knocked it down to <1%. Still holding its breath though. (Auto-resolved: no updates in 24h)
// The official story
Incident with Pull Requests
// Status page says
Nov 13 , 16:12 UTC Update - We’ve taken mitigating action to resolve the problem of merge requests timing out. This issue initially impacted 3% of requests and is now down to less than 1%. We continue to monitor recovery. Nov 13 , 16:09 UTC Update - Pull Requests is experiencing degraded performance. We are continuing to investigate. Nov 13
🔗 Official status page (for the PR-approved version)
https://www.githubstatus.com/incidents/1xzmt89vv61lGithub's Greatest Hits
🟢 GITHUB
4d ago
🟠 Copilot's MAI Code 2 Flash decided to ghost developers harder than your ex. GitHub's been playing tech support therapist with their upstream provider and things are allegedly 'improving' now. Translation: they hit it with a wrench and some prayers. (Auto-resolved: no updates in 24h)
🟢 GITHUB
Nov 09, 2026
🟠 Ghost traffic flooded GitHub like uninvited guests at a concert—anonymous users triggered a 504 timeout tsunami. CI/CD pipelines are learning what rejection feels like, and release downloads are practicing patience. The cure? Log in or watch your deploys die silently. (Auto-resolved: no updates in 24h)
🟢 GITHUB
Oct 07, 2026
🟠 GitHub decided to ghost developers twice in one day—Git ops, Issues, Actions, and PRs all took an unscheduled siesta from 16:52-17:01 UTC. Systems are back online, but the incident playlist is starting to feel like a broken record. (Auto-resolved: no updates in 24h)
🟢 GITHUB
Aug 17, 2026
🔴 GitHub decided to play roulette with your API calls—20% of them lose. Archive downloads? Those are running at 50% failure, which is basically a coin flip. Root cause still a mystery, like finding a specific commit in a monorepo at 2am. (Auto-resolved: no updates in 24h)