GitHub experienced a critical incident on August 26, 2026 affecting Actions and Pages, lasting 2h 49m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Aug 26, 2026, 03:11 PM UTC
We are investigating reports of degraded availability for Actions
- investigating Aug 26, 2026, 03:12 PM UTC
Pages is experiencing degraded performance. We are continuing to investigate.
- investigating Aug 26, 2026, 03:23 PM UTC
We've identified an issue with a database primary and are failing over to a replica immediately
- investigating Aug 26, 2026, 03:48 PM UTC
primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
- investigating Aug 26, 2026, 04:14 PM UTC
We believe we've identified and addressed the issue and are ramping traffic back up slowly to ensure it doesn't recur. Some customers will continue to see delays as we ramp up.
- investigating Aug 26, 2026, 04:49 PM UTC
Pages is operating normally.
- investigating Aug 26, 2026, 04:50 PM UTC
We are continuing to observe recovery and delayed queues are burning down. Some customers will continue to see increased delays until all throttled work has been completed - we expect this within the next hour.
- investigating Aug 26, 2026, 05:32 PM UTC
We are continuing to observe recovery and expect actions inbound queues to be back to normal in <30min. Work will continue to flow through the system subject to per-customer concurrency limits.
- monitoring Aug 26, 2026, 05:54 PM UTC
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- monitoring Aug 26, 2026, 06:00 PM UTC
All inbound queues have recovered and Actions is operating as expected. 3.7% of jobs assigned to larger runners during the early stage of this incident are stuck waiting for runner assignment. Those will be canceled within the hour. Other runners are successfully processing all new jobs.
- resolved Aug 26, 2026, 06:01 PM UTC
This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.