What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with GitHub now? Check the current statusAffected services
Updates (6)
- Aug 27, 2026, 12:26 AMIncident with Actions and Pull Requests
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 resu
GitHub ↗ - Aug 27, 2026, 12:26 AMIncident with Actions and Pull Requests
The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Aug 27, 2026, 12:25 AMIncident with Actions and Pull Requests
We confirmed full recovery beginning at 23:58 UTC. Actions workflow runs and pull request merges are operating normally. We will now resolve the incident while continuing to monitor service health.
GitHub ↗ - Aug 27, 2026, 12:01 AMIncident with Actions and Pull Requests
We've applied mitigations and are seeing recovery in Actions workflow runs and blocked pull request merges. We're continuing to monitor for sustained health of merge commit creates before resolving.
GitHub ↗ - Aug 26, 2026, 10:57 PMIncident with Actions and Pull Requests
We are investigating elevated delays and timeouts affecting Actions workflow runs triggered by pull request events. 20% of actions runs have delayed starts of more than 5 minutes and up to 4% of runs failed to trigger. We are actively working on mitigation and will provide updates as we learn more.
GitHub ↗ - Aug 26, 2026, 10:56 PMIncident with Actions and Pull Requests
We are investigating reports of degraded performance for Actions and Pull Requests
GitHub ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow GitHub's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.