GITHUB

⚪ GitHub's Issues and Pull Requests decided to ghost both authenticated and unauthenticated users for 100 minutes straight. 10% of requests got the silent treatment at peak, which is apparently what happens when you give a service too much power over developer sanity. The good news: it's resolved now. The bad news: your code review is still pending from 2019. (Auto-resolved: no updates in 24h)

⏰ Jan 19, 2026 Fixed (for now) spotted via status_rss

// The official story

Incident with Issues and Pull Requests

// Status page says

Jan 15 , 18:54 UTC Resolved - On January 15, 2026, between 16:40 UTC and 18:20 UTC, we observed increased latency and timeouts across Issues, Pull Requests, Notifications, Actions, Repositories, API, and Account Login. An average 1.8% of combined web and API requests saw failure, peaking briefly at 10% early on. The majority of impact was observed for unauthenticated users, but authenticated users were impacted as well. Thi

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

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

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)