← Back to the carnage
GITHUB
⚪ GitHub decided OpenAI models needed a mental health day, so they ghosted users for a few hours. Engineers frantically rerouted traffic to the B-team models while pretending everything was fine. Crisis averted, dignity not included. (Auto-resolved: no updates in 24h)
// The official story
Disruption with OpenAI Models
// Status page says
May 28 , 20:41 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. May 28 , 20:06 UTC Update - Open AI models are currently unavailable. We are shifting requests to other models to reduce impact. May 28</
🔗 Official status page (for the PR-approved version)
https://www.githubstatus.com/incidents/rhqcgg8lg6mmGithub'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)