Incident with Actions

Timeline

1. 15:11 UTC GitHub status page · Reported Incident with Actions
2. 15:11 UTC GitHub status page · Investigating We are investigating reports of degraded availability for Actions
3. 15:12 UTC GitHub status page · Investigating Pages is experiencing degraded performance. We are continuing to investigate.
4. 15:23 UTC GitHub status page · Investigating We've identified an issue with a database primary and are failing over to a replica immediately
5. 15:48 UTC GitHub status page · Investigating primary failover briefly improved performance but did not fully mitigate, we've throttled inbound traffic and are investigating upstream Vitess issues
6. 16:14 UTC GitHub status page · Investigating 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.
7. 16:49 UTC GitHub status page · Investigating Pages is operating normally.
8. 16:50 UTC GitHub status page · Investigating 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.
9. 17:32 UTC GitHub status page · Investigating We are continuing to observe recovery and expect actions inbound queues to be back to normal in
10. 17:54 UTC GitHub status page · Monitoring The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
11. 18:00 UTC GitHub status page · Monitoring 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.
12. 18:01 UTC GitHub status page · Resolved On August 26, 2026 from 15:02 to 15:45 UTC, Actions jobs failed to start. The following 2 hours until 17:40 UTC, Actions runs were delayed starting by more than 5 minutes as the system caught up with delayed load. This impact was triggered by saturation of writes to the database primary used by the service processing triggers for Actions workflows. The primary was failed over, but the system did not fully recover. The saturation was caused by growing daily peak load combined with an upstream issue in GitHub’s event processing infrastructure…