GITHUB

⚪ Some GitHub users got the 503 treatment after a surprise traffic tsunami hit on May 15th. Engineers found the culprit, kicked it out, and normal chaos resumed. The 'subset of customers' who got ghosted are now back online. (Auto-resolved: no updates in 24h)

⏰ May 15, 2026 Fixed (for now) spotted via status_rss

// The official story

[Retroactive] Incident with GitHub.com

// Status page says

May 15 , 02:30 UTC Resolved - Beginning at 02:49 UTC on May 15 2026 and lasting until 03:04 UTC, GitHub.com was unavailable for a subset of customers. This impact has been mitigated and normal service resumed. The issue was rooted in a sudden spike in traffic, with intermittent impact. We've identified the source of the traffic and prevented further disruption.

🔗 Official status page (for the PR-approved version)

https://www.githubstatus.com/incidents/t5mch8tlq6vl

Github's Greatest Hits

🟢 GITHUB 6d ago

🟠 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)

🟢 GITHUB Aug 12, 2026

🟡 GitHub's decided logins and asset downloads need a 'thinking break.' Engineers are currently in that special Slack-based panic state they call 'investigating.' Classic move: auth systems remember passwords better than uptime. (Auto-resolved: no updates in 24h)

🟢 GITHUB Aug 12, 2026

🟡 GitHub users reporting degraded logins and package downloads while engineers squint at dashboards pretending this is fine. The 'investigating' status translates to 'we have no idea yet but coffee is being consumed.' At least they're honest about not knowing what broke. (Auto-resolved: no updates in 24h)