GITHUB

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

⏰ Aug 17, 2026 Fixed (for now) spotted via status_rss

// The official story

Incident with GitHub.com

// Status page says

Aug 17 , 14:04 UTC Update - We are experiencing high error rates around 20% for web experiences and api traffic. Archive downloads and raw repository content downloads are experiencing an approximate 50% error rate. Investigations are on-going into the root cause, and updates will continue to be provided as we investigate. Aug 17 , 13:58 UTC Update - Pull Requests is

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

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

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

🟢 GITHUB Jul 20, 2026

🔴 GitHub Actions workflow runners went offline July 20th and knocked over a domino trail of other services. Engineers are thrashing on mitigation while the incident spawns sibling incidents like a tech family drama episode. Your CI/CD pipeline is now a CI/CD pipe dream. (Auto-resolved: no updates in 24h)