What Happened
GitHub experienced an outage on April 1, 2026. The incident lasted approximately 8 hours 40 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 |
|---|---|---|
| 12:10 | Monitoring | The success rate and latency for creating and viewing agent sessions has stabilized at baseline levels, we are continuing to monitor recovery |
| 12:02 | Monitoring | The degradation has been mitigated. We are monitoring to ensure stability. |
| 11:37 | Monitoring | The success rate for creating and viewing agent sessions has stabilized, and we're continuing to monitor latency, which is trending toward baseline levels. |
| 11:24 | Monitoring | The degradation has been mitigated. We are monitoring to ensure stability. |
| 10:56 | Monitoring | The degradation affecting Copilot has been mitigated. We are monitoring to ensure stability. |
| 10:31 | Investigating | Users may see increased latency and intermittent errors when viewing or creating agent sessions. We are working on mitigations to return to baseline performance and success rate. |
| 10:00 | Investigating | We are investigating reports of issues with service(s): Copilot Dotcom Agents. We will continue to keep users updated on progress towards mitigation. |
| 09:58 | Investigating | We are investigating reports of degraded performance for Copilot |
| 22:00 | Investigating | We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic. |
| 19:37 | Investigating | We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours. |
| 17:48 | Investigating | We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April ... |
| 16:00 | Investigating | We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic config... |
| 15:02 | Investigating | We are investigating reports of impacted performance for some GitHub services. |
| 23:50 | Resolved | All systems operational |
Impact
The outage lasted approximately 8 hours 40 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 →