Rezolvat · a durat 1 h

Pană GitHub pe 12 octombrie

Raportările pentru GitHub au urcat la 168 pe oră și au rămas ridicate timp de 1 h.

Început
14:00
12 octombrie 2026 · UTC
Revenit la normal
15:00
1 h mai târziu
Vârf
168/oră
4× față de normal
Incidentul GitHub
7 h 54 min
Incident with Actions, Pull Requests and Issues

Raportări în timpul penei

12:0016:50 UTC

Ce a spus GitHub

www.githubstatus.com
Rezolvat12:21–20:16 · 7 h 54 min

Incident with Actions, Pull Requests and Issues

  1. Rezolvat · 20: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.

  2. În curs de investigare · 19:28

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

  3. În curs de investigare · 17:34

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

  4. În curs de investigare · 15:50

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

  5. În curs de investigare · 15: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.

  6. În curs de investigare · 14:37

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

  7. În curs de investigare · 14:36

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

  8. În curs de investigare · 14:35

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

  9. În curs de investigare · 13: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.

  10. În curs de investigare · 13:02

    Pull Requests is operating normally.

  11. În curs de investigare · 12:57

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

  12. În curs de investigare · 12: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.

  13. În curs de investigare · 12:21

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

GitHub este oprit acum?

Status în timp real, raportările de azi și alte pene anterioare.

Statusul GitHub acum →