GitHub incident
Actions and Codespaces APIs experiencing partial failures
GitHub experienced a major incident on July 7, 2026 affecting Actions and Codespaces, lasting 2h 2m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Jul 07, 2026, 02:14 PM UTC
We are investigating reports of degraded performance for Actions and Codespaces
- investigating Jul 07, 2026, 02:14 PM UTC
Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a small percentage of the time. Actions runs in progress are continuing successfully.
- investigating Jul 07, 2026, 02:32 PM UTC
Codespaces is experiencing degraded availability. We are continuing to investigate.
- investigating Jul 07, 2026, 02:47 PM UTC
Customers accessing the Actions and Codespaces REST APIs may see 500 class errors a percentage of the time. Retries may be successful. Actions runs and codespaces in progress are continuing successfully. We are continuing to investigate the source of these errors.
- investigating Jul 07, 2026, 03:06 PM UTC
Customers accessing Actions runners and Codespaces REST APIs continue to see 500 errors a percentage of the time. Retries may be successful. We continue to investigate the source of these errors.
- investigating Jul 07, 2026, 03:50 PM UTC
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 Jul 07, 2026, 04:00 PM UTC
We have rolled out the mitigation and are seeing recovery.
- monitoring Jul 07, 2026, 04:02 PM UTC
The degradation affecting Actions and Codespaces has been mitigated. We are monitoring to ensure stability.
- resolved Jul 07, 2026, 04:17 PM UTC
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.