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 (4)
- Aug 24, 2026, 02:34 PMActions delays in starting runs
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. <br /> <br />The incident was caused by a disk failure on a node hosting one of many service instances responsible for processing runner assignment events. Typically, pods on unhealthy nodes are removed and replaced automatically without impact. In this case, although the node was severely degraded and unable to perform disk operations, it continued sending healthy signals, preventing the system from immediately moving its work elsewher
GitHub ↗ - Aug 24, 2026, 02:26 PMActions delays in starting runs
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Aug 24, 2026, 02:22 PMActions delays in starting runs
Failures while queuing and running Actions jobs for a subset of customers are now resolving. We are monitoring for full recovery.
GitHub ↗ - Aug 24, 2026, 01:56 PMActions delays in starting runs
We are investigating reports of degraded performance for Actions
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.