GitHub outage hits PRs, issues, git, API
GitHub reported and then resolved an incident on May 27, 2026, that caused degraded performance across API Requests, Git Operations, Issues, and Pull Requests. The status page shows the issue was first investigated at 12:10 UTC, updated at 12:54 UTC, and marked resolved at 13:16 UTC, with GitHub promising a root cause analysis later. For teams that live in GitHub all day, this is a workflow outage, not just a platform blemish.
Hot take: GitHub’s reliability story is still strong overall, but when it slips, it tends to hit the exact surfaces developers depend on most, so the pain compounds fast.
- –The blast radius covered core day-to-day workflows: code pushes/pulls, issue tracking, PR review, and API-driven automation.
- –The incident was short-lived, but even a sub-hour degradation can stall CI/CD, automations, and merge flow across many teams.
- –GitHub resolved it quickly and was transparent about the timeline, but the recurring pattern reinforces how operationally central the platform has become.
- –This is infrastructure risk, not a product feature issue, which makes the operational resilience of GitHub itself the real product concern.
DISCOVERED
46d ago
2026-05-28
PUBLISHED
46d ago
2026-05-27
RELEVANCE
AUTHOR
maxnoe