Delayed Actions status check results
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. <br /><br />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. <br /><br />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. (Affected: Actions)
Started
Oct 23, 2026, 7:29 AM UTC
Resolved
Oct 23, 2026, 8:05 AM UTC
Duration
36m
Verified sources
Incident Detail
We are investigating reports of degraded performance for Actions
We are seeing delays in results from Actions workflows being reported within GitHub starting from 07:07 UTC.<br /><br />Recovery is already being seen but our team is continuing to investigate and monitor performance.
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
As of 07:27 UTC, Actions results are delivering within normal SLOs again.<br /><br />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.
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. <br /><br />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. <br /><br />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.