What Happened
GitHub experienced an outage on April 27, 2026. The incident lasted approximately 4 hours 30 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 |
|---|---|---|
| 16:27 | Investigating | We are investigating reports of degraded performance for Actions |
| 22:44 | Monitoring | The degradation has been mitigated. We are monitoring to ensure stability. |
| 22:35 | Monitoring | The degradation has been mitigated. We are monitoring to ensure stability. |
| 21:33 | Monitoring | The degradation affecting Actions, Issues, Packages and Pull Requests has been mitigated. We are monitoring to ensure stability. |
| 21:32 | Investigating | We've applied a mitigation and continuing to monitor |
| 20:06 | Investigating | Pull Requests is experiencing degraded performance. We are continuing to investigate. |
| 19:50 | Investigating | We have identified the source of the additional load causing stress on our ElasticSearch clusters. We have disabled the source of that load and are seeing signs of recovery |
| 18:19 | Investigating | Pull Requests is experiencing degraded availability. We are continuing to investigate. |
| 18:17 | Investigating | We're continuing to see connectivity issues reaching elasticsearch. Impact on downstream services will be intermittent as we find the root cause |
| 17:35 | Investigating | Users are experiencing intermittent failures to view issues, pull requests, projects and Actions workflow runs.<br /><br />We are still investigating and attempting mitigations. We will provide fur... |
| 16:53 | Investigating | Pull Requests is experiencing degraded performance. We are continuing to investigate. |
| 16:39 | Investigating | Packages is experiencing degraded performance. We are continuing to investigate. |
| 16:36 | Investigating | Issues is experiencing degraded performance. We are continuing to investigate. |
| 16:33 | Investigating | Customers across GitHub are experiencing failures with searches. Examples include: workflow run failures, projects failing to load, and timed out search requests. This is due to an ongoing infrastr... |
| 16:31 | Investigating | We are investigating reports of degraded performance for Actions |
| 17:26 | Investigating | We've found the issue and are working on deploying a solution to get Codex agent runs working again. |
| 17:01 | Investigating | Copilot Cloud Agent (CCA) jobs using the Codex agent are failing after starting. To avoid this issue, please choose a different agent. We are investigating the cause and working towards remediation |
| 16:48 | Investigating | We are investigating reports of impacted performance for some GitHub services. |
| 22:51 | Resolved | All systems operational |
Impact
The outage lasted approximately 4 hours 30 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 →