Actions and Codespaces APIs experiencing partial failures

[investigating] We are investigating reports of degraded performance for Actions and Codespaces

[investigating] Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time.<br /><br />Actions runs in progress are continuing successfully.

[investigating] Codespaces is experiencing degraded availability. We are continuing to investigate.

[investigating] Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time.  Retries may be successful.<br /><br />Actions runs and codespaces  in progress are continuing successfully.<br /><br />We are continuing to investigate the source of these errors.

[investigating] Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful.<br /><br />We continue to investigate the source of these errors.

[investigating] Customers will continue to see 500 errors for approximately 8% of Actions runner REST APIs and 13% of Codespaces REST APIs. Retries may be successful. We have identified a likely cause and are preparing a mitigation.

[investigating] We have rolled out the mitigation and are seeing recovery.

[monitoring] The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability.

[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.

[resolved] On July 7, 2026, between 14:01 UTC and 16:17 UTC the Actions and Codespaces REST APIs were degraded and returned intermittent 500-class errors for a percentage of requests. Error rates peaked at approximately 8% of Actions runner API requests and 13% of Codespaces API requests, though retries were frequently successful. In-progress Actions runs and Codespaces were not impacted and continued successfully. This was due to a recent change that did not deliver the expected performance and, under certain conditions, caused downstream errors.<br /><br />We mitigated the incident by rolling back the change, after which the affected services recovered.<br /><br />We are working to improve the resilience of our services to these conditions and to strengthen our monitoring to reduce our time to detection and mitigation of issues like this one in the future.