What Happened
GitHub experienced an outage on May 6, 2026. The incident lasted approximately 2 hours 25 minutes.
World's largest source code hosting platform with version control, CI/CD (Actions), code review, project management, and AI coding assistant (Copilot).
Timeline
| Time (UTC) | Status | Details |
|---|---|---|
| 17:11 | Investigating | Actions is experiencing degraded performance. We are continuing to investigate. |
| 17:11 | Investigating | Standard hosted runners have now reached full recovery. Hosted Runners with Private Networking in the East US region remain degraded as we continue working with our compute provider to restore capa... |
| 16:33 | Investigating | We've seen signs of recovery for Standard Hosted Runners and are continuing to monitor for full recovery. Hosted Runners with Private Networking in the East US region remain affected as we continue... |
| 15:54 | Investigating | We've applied a mitigation for long queue times and failures on Standard Hosted Runners and are monitoring for full recovery. Hosted Runners with Private Networking in the East US region remain aff... |
| 15:12 | Investigating | We are working with our compute provider to alleviate elevated queue times and failures for Actions Jobs running on Hosted Runners in the East US region affecting 10% of runs. Hosted Runners with p... |
| 14:14 | Investigating | We are investigating elevated queue times and failures on Actions Jobs running on Hosted Runners in East US affecting 8% of runs. Hosted Runners with private networking can fail over to a different... |
| 13:48 | Investigating | We are investigating elevated queue times on Actions Jobs running on Standard Hosted Runners in East US affecting 10% of runs |
| 13:37 | Investigating | We are investigating reports of degraded availability for Actions |
| 18:25 | Monitoring | The degradation affecting Git Operations has been mitigated. We are monitoring to ensure stability. |
| 17:26 | Investigating | We're continuing to work on preventing further impact from the earlier issue. No SSH-based impact is expected at this time. We'll post new updates if impact recurs or once our mitigation is in place. |
| 17:23 | Investigating | Git Operations is experiencing degraded performance. We are continuing to investigate. |
| 16:54 | Monitoring | Between approximately 14:00 and 16:10 UTC, customers using SSH-based Git operations may have experienced elevated latency and failures. HTTP-based operations were not impacted. We've identified a s... |
| 16:49 | Investigating | We are investigating reports of impacted performance for some GitHub services. |
| 09:19 | Monitoring | The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. |
| 09:08 | Investigating | We've applied a mitigation to fix the issues with queuing and running Actions jobs. We are seeing improvements in telemetry and are monitoring for full recovery. |
| 08:00 | Investigating | Actions is experiencing issues with ubuntu standard hosted runners leading to high wait times. We are actively investigating the issue |
| 07:19 | Investigating | We are investigating reports of degraded availability for Actions |
| 09:46 | Resolved | All systems operational |
Impact
The outage lasted approximately 2 hours 25 minutes. GitHub runs on Azure — check those status pages if you experienced cascading issues.
Resolution
GitHub has recovered and is now operational.
What To Do Next
- View GitHub live status and outage history
- Set up alerts to get notified instantly next time GitHub has an issue
- Compare GitHub reliability with other services
---
This post was automatically generated by ServiceAlert.ai's monitoring system. View live status →