GitHub experienced a significant incident on October 12, 2026, affecting multiple core platform features. According to GitHub’s status page, the company began investigating reports of degraded performance for Actions, Issues, and Pull Requests at 12:21 UTC.
At 12:33 UTC, GitHub provided details on the scope of the incident, noting that users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews through both REST and GraphQL APIs.
GitHub initiated mitigation efforts at 12:57 UTC and noted that users might also experience delayed web notifications during the process. By 13:02 UTC, Pull Requests returned to normal operation.
The company’s initial mitigation attempt was not fully successful. At 13:38 UTC, GitHub reported that users may still experience delays and errors with Actions, issues, and projects, while notifications remained delayed. The company indicated it was continuing to investigate the root cause and work on additional mitigations.
By 14:35 UTC, GitHub had mitigated the degradation affecting Issues and reported it was monitoring for stability. The following minute, at 14:36 UTC, the degradation affecting Actions was also mitigated, with GitHub continuing to monitor the service.
At 14:37 UTC, GitHub confirmed it had mitigated issues with Actions, issues, and projects, and reported a mitigation in progress for the notification delay.
Finally, at 15:19 UTC, GitHub announced it had successfully applied a mitigation for notifications and that notifications had resumed. However, the company noted that notifications would continue to be delayed as it worked through a backlog of pending alerts.
The incident highlighted potential vulnerabilities in GitHub’s infrastructure, though the company’s response timeline showed relatively quick mitigation of most service degradations. Users relying on GitHub Actions for CI/CD pipelines, issue tracking, and code review features were affected during the approximately three-hour incident window.
Key facts
- GitHub experienced degraded performance affecting Actions, Issues, and Pull Requests on Oct 12, 2026
- Users reported issues loading the Actions tab UI, queueing new Actions runs, creating and updating issues, and requesting PR reviews
- Pull Requests returned to normal operation by 13:02 UTC
- Actions and Issues degradation were mitigated by 14:36 UTC
- Notifications resumed by 15:19 UTC but continued to be delayed due to a backlog