Summary
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.
Impact
critical
Timeline
[investigating] We are investigating reports of degraded performance for Actions
via statuspage[investigating] We are investigating degraded availability for GitHub Actions on github.com and in GHEC DR stamps. New workflows may delay or fail to start, and ongoing runs may fail. We will provide more information as soon as we can.
via statuspage[investigating] We have identified the cause of failures in GitHub Actions and are working to restore service.
via statuspage[investigating] API Requests is experiencing degraded availability. We are continuing to investigate.
via statuspage[investigating] Actions is experiencing degraded availability. We are continuing to investigate.
via statuspage[investigating] Actions is experiencing degraded performance. We are continuing to investigate.
via statuspage[investigating] Actions and Pages are experiencing degraded performance. We are continuing to investigate.
via statuspage[investigating] Issues is experiencing degraded performance. We are continuing to investigate.
via statuspage[investigating] We continue to work on mitigative efforts to restore Actions workflow runners, and have observed that the extended downtime has started to cause knock-on effects to other services.<br /><br />A separate incident was opened before we understood they were related. We will continue to post updates on this incident.
via statuspage[investigating] Pages is operating normally.
via statuspage[investigating] Issues is operating normally.
via statuspage[investigating] API Requests is experiencing degraded performance. We are continuing to investigate.
via statuspage[investigating] Issues, API Requests, and Pages have recovered. We are continuing to work on restoring GitHub Actions jobs using self-hosted or larger-hosted runners.
via statuspage[investigating] API Requests is operating normally.
via statuspage[investigating] We’re seeing recovery across all impacted Actions runners. The team is continuing to monitor for global recovery.
via statuspage[monitoring] The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
via statuspage[monitoring] Actions has fully recovered, and we will continue to monitor the platform to ensure stability.
via statuspage[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.
via statuspageLessons Learned
⚠GitHub has experienced 116 incidents in the past year. This frequency suggests systemic reliability challenges that may warrant additional monitoring.
📊Incidents related to api have occurred 745 times across all providers in the past year. This is one of the most common failure categories in cloud infrastructure.
💡This incident is categorized as: API Issue. Consider implementing preventive measures specific to this failure category.