Live / Incidents / GitHub Copilot
GitHub Copilot: Incident with Actions and Pull Requests
GitHub Copilot · github.comImpact: minorResolved2026-08-27 00:26 UTC
Public — what happened
Summary
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. Some users also experienced delays in pull request merge-commit generation, mergeability information, and merge-button availability. Actions and Pull Requests fully recovered by 23:58 UTC; the incident was resolved at 00:26 UTC after normal operation was confirmed. <br /><br />Background jobs that process pull request updates and generate merge commits were impacted by timeouts reaching a single partition of git data. This resulted in a backlog in pull request merge-commit processing, delaying pull request-triggered GitHub Ac
Timeline
- Started — 2026-08-26 22:56 UTC
- Last update — 2026-08-27 00:26 UTC
- Resolved — 2026-08-27 00:26 UTC
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GitHub Copilot against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GitHub Copilot: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GitHub Copilot report →