GitHub: Delayed Actions status check results
Affected components: Actions
Timeline of updates
- investigating
We are investigating reports of degraded performance for Actions
- investigating
We are seeing delays in results from Actions workflows being reported within GitHub starting from 07:07 UTC.
Recovery is already being seen but our team is continuing to investigate and monitor performance. - monitoring
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
- monitoring
As of 07:27 UTC, Actions results are delivering within normal SLOs again.
Thank you for this patience during this period of delayed Actions results delivery. Our team continues to monitor system health and explore refinements to reduce impact to customers in the future. - resolved
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.
Changes Rewindex caught on this incident
- Incident updated: Delayed Actions status check results
- Incident updated: Delayed Actions status check results
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
cd047fb46488188f…Version 2 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
90861049760b3034…Version 3 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
2aac1f67e5d09752…
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).