What visitors reported during this incident
No visitor reports were filed for this incident.
Having problems with GitHub now? Check the current statusAffected services
Updates (13)
- Oct 12, 2026, 08:16 PMIncident with Actions, Pull Requests and Issues
On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. <br /><br />The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC. <br /><br />The incident was triggered through a latent condition in our notificatio
GitHub ↗ - Oct 12, 2026, 07:28 PMIncident with Actions, Pull Requests and Issues
Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.
GitHub ↗ - Oct 12, 2026, 05:34 PMIncident with Actions, Pull Requests and Issues
Web and email notifications continue to be delayed as we work through a backlog of notifications.
GitHub ↗ - Oct 12, 2026, 03:50 PMIncident with Actions, Pull Requests and Issues
Notifications have resumed but will continue to be delayed as we work through a backlog.
GitHub ↗ - Oct 12, 2026, 03:19 PMIncident with Actions, Pull Requests and Issues
We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.
GitHub ↗ - Oct 12, 2026, 02:37 PMIncident with Actions, Pull Requests and Issues
We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.
GitHub ↗ - Oct 12, 2026, 02:36 PMIncident with Actions, Pull Requests and Issues
The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Oct 12, 2026, 02:35 PMIncident with Actions, Pull Requests and Issues
The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.
GitHub ↗ - Oct 12, 2026, 01:38 PMIncident with Actions, Pull Requests and Issues
Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations.
GitHub ↗ - Oct 12, 2026, 01:02 PMIncident with Actions, Pull Requests and Issues
Pull Requests is operating normally.
GitHub ↗ - Oct 12, 2026, 12:57 PMIncident with Actions, Pull Requests and Issues
We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.
GitHub ↗ - Oct 12, 2026, 12:33 PMIncident with Actions, Pull Requests and Issues
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, including via REST and GraphQL APIs.
GitHub ↗ - Oct 12, 2026, 12:21 PMIncident with Actions, Pull Requests and Issues
We are investigating reports of degraded performance for Actions, Issues and Pull Requests
GitHub ↗
What to do next
- Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
- Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
- Watch the provider going forward. Follow GitHub's status feed →
GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.