‹ Back to incident history

Incident with Actions, Pull Requests and Issues

ResolvedMinor incidentGitHub
Monday, October 12, 2026 20:21 – Tuesday, October 13, 2026 04:16 (7 hr 54 min)
Affected components
Issues
Pull Requests
Actions
Updates
ResolvedTuesday, October 13, 2026 04:16

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 notifications delivery pipeline that put a high volume of an expensive query on our sharded database replicas. This reduced available database capacity to serve requests for Issues, Pull Requests, Projects, and Actions.<br /><br />We have fixed the notifications pipeline’s code path that issued the expensive query. We are also improving resilience of the database layer to reduce the likelihood and impact of similar incidents.

InvestigatingTuesday, October 13, 2026 03:28

Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications.

InvestigatingTuesday, October 13, 2026 01:34

Web and email notifications continue to be delayed as we work through a backlog of notifications.

InvestigatingMonday, October 12, 2026 23:50

Notifications have resumed but will continue to be delayed as we work through a backlog.

InvestigatingMonday, October 12, 2026 23:19

We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog.

InvestigatingMonday, October 12, 2026 22:37

We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications.

InvestigatingMonday, October 12, 2026 22:36

The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

InvestigatingMonday, October 12, 2026 22:35

The degradation affecting Issues has been mitigated. We are monitoring to ensure stability.

InvestigatingMonday, October 12, 2026 21:38

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.

InvestigatingMonday, October 12, 2026 21:02

Pull Requests is operating normally.

InvestigatingMonday, October 12, 2026 20:57

We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate.

InvestigatingMonday, October 12, 2026 20:33

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.

InvestigatingMonday, October 12, 2026 20:21

We are investigating reports of degraded performance for Actions, Issues and Pull Requests

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview