IT intelligence

An internal cleanup task overloaded a shared GitHub database on September 13, 2026, disrupting roughly 28 services, GitHub reports. About 96% of attempts to create issues through the website failed, while token failures also affected Actions workflows. GitHub paused the job and reduced internal load; services recovered by 10:44 UTC. Its incident review calls for broader load safeguards, bounded retries and database separation.

Sep 4, 22:23 UTC Resolved - On September 4, 2026, between approximately 21:45 and 22:07 UTC, some users experienced errors and elevated latency for repository operations. The incident was fully resolved at 22:23 UTC.

GitHub users saw stale pull-request diffs during a resolved September 1, 2026, processing slowdown. GitHub says a concentrated surge of pushes overwhelmed background workers while autoscaling failed to add capacity as intended. At the peak, median diff refresh time exceeded two minutes, versus roughly three seconds normally. Pushing commits and opening pull requests still worked. Manual capacity increases cleared the backlog by approximately 16:01 UTC.

Aug 27, 19:44 UTC Resolved - On August 26, 2026, between 20:40 UTC and 00:51 UTC on August 27, GitHub Billing experienced degraded performance affecting billing budget pages and GitHub Copilot CLI sessions.

Aug 27, 00:26 UTC Resolved - On August 26, 2026, from 21:55 UTC to 23:58 UTC, 2.6% of workflow runs triggered by pull request events were delayed, with the impact rising as high as 25% at its peak.

Aug 24, 14:34 UTC Resolved - On August 24, 2026, between 13:33 UTC and 14:04 UTC, 3.8% of Actions runs experienced start delays over 5 minutes with 1.25% of Actions runs failing outright.

Aug 24, 07:58 UTC Resolved - On August 24th, 2026, between approximately 06:35 and 07:25 UTC, the Copilot service experienced a degradation of the Claude Fable 5 model due to an issue with our upstream provider.