Incident with Actions, Pull Requests and Issues

Users may encounter unexpected delays or errors when performing routine development tasks on GitHub.

On October 12, 2026, GitHub experienced a significant incident impacting core functionalities including Actions, Issues, and Pull Requests. The issue began around 12:21 UTC with reports of degraded performance across these services. By 12:33 UTC, users encountered problems loading the Actions tab, interacting with the Checks API, queueing Actions runs, and creating/updating issues, alongside API-related issues for Pull Requests. Initial mitigation efforts at 13:38 UTC were not fully successful, leading to continued delays and errors, and also affecting web notifications. By 14:35 UTC, the degradation affecting Issues was mitigated, followed by Actions at 14:36 UTC. A mitigation was in progress for delayed notifications, and Pull Requests were reported as operating normally by 13:02 UTC.

This incident highlights the interconnectedness of GitHub's core development tools and the cascading effects when one component fails. The simultaneous degradation of Actions, Issues, and Pull Requests suggests a shared underlying infrastructure or dependency that requires careful monitoring and robust failover mechanisms. The impact on API interactions, including the Checks API and REST/GraphQL APIs, underscores the critical role these services play for automated workflows and third-party integrations.

The slow recovery and the need for multiple mitigation attempts point to potential complexities in diagnosing and resolving the root cause. The delays in notifications also indicate that system-wide communication channels can be vulnerable. As platforms increasingly centralize developer workflows, the resilience and reliability of these services become paramount for maintaining developer productivity and trust.