CompaniesGitHub CopilotIncidents
GitHub Copilot: 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. - resolvedEdited
On October 23, 2026, between 07:06 UTC and 07:27 UTC, GitHub Actions workflow run results were delayed. Job status, check run updates, and logs in the GitHub UI and API updated with an average delay of about 2 minutes, and some updates were delayed by up to about 7 minutes.
During this window, a storage dependency that Actions uses to process workflow logs and artifacts throttled our requests. This slowed result processing, causing updates to queue up. The queue was fully processed by 07:27 UTC, shortly after the throttling stopped.
To reduce the risk of recurrence, we have added several storage accounts to increase capacity, and we are working on additional steps to continue to scale. We are also working with our storage provider to understand why the throttling occurred, and improving how result processing handles storage throttling and how quickly we detect it.
Changes Rewindex caught on this incident
- Incident updated: Delayed Actions status check results
- Incident updated: Delayed Actions status check results
- Incident silently edited: 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
374d0d53d393ed3c…Version 2 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
f59e30ad744ba037…Version 3 captured
In the 2026-10-23 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6d0015a5d3ab624c…Version 4 captured
In the 2026-10-28 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3a56646fbf04bf6c…
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by GitHub Copilot, started 2026-10-23 07:31 UTC, resolved after 34 min, 5 update(s); edited after publishing.
- Title
- Delayed Actions status check results
- Vendor
- GitHub Copilot
- Date
- URL
- https://rewindex.com/company/github-copilot/incidents/ntrfd2jqldn6
GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on October 23, 2026GitHub Copilot in October 2026MarkdownJSON