Incident with Dependabot

Timeline

1. 04 Nov · 22:04 UTC 🟠 Resolved atom

   Oct 30, 23:29 UTC
   Resolved - On October 30, 2026, between 20:15 and 21:56 UTC, an advisory-publication-driven fan-out caused an unexpected saturation of network connections to the Dependabot alerts datastore. During this period we observed a high rate of write failures on this datastore; users saw elevated failure rates when dismissing or resolving Dependabot alerts, as well as failures when linking Dependabot update pull requests to Dependabot security alerts.  We also observed delays in creating and updating security alerts that extended through November 2, 2026.
   
   The unexpected fan-out was caused by a missing job queue throttle after the queues for the fan-out work were migrated as part of system maintenance. We have restored the fan-out throttle and further isolated and throttled these processes to guard against further disruptions.
   
   Oct 30, 22:32 UTC
   Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
   
   Oct 30, 22:32 UTC
   Update - We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
   
   Oct 30, 21:44 UTC
   Update - We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
   
   Oct 30, 21:00 UTC
   Update - We are investigating elevated errors when viewing some Dependabot alerts.
   
   Oct 30, 20:59 UTC
   Investigating - We are investigating reports of impacted performance for some GitHub services.

2. 30 Oct · 23:29 UTC 🟡 Resolved atom

   Oct 30, 23:29 UTC
   Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.
   
   Oct 30, 22:32 UTC
   Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
   
   Oct 30, 22:32 UTC
   Update - We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
   
   Oct 30, 21:44 UTC
   Update - We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
   
   Oct 30, 21:00 UTC
   Update - We are investigating elevated errors when viewing some Dependabot alerts.
   
   Oct 30, 20:59 UTC
   Investigating - We are investigating reports of impacted performance for some GitHub services.

3. 30 Oct · 22:32 UTC 🟡 Monitoring atom

   Oct 30, 22:32 UTC
   Monitoring - The degradation has been mitigated. We are monitoring to ensure stability.
   
   Oct 30, 22:32 UTC
   Update - We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
   
   Oct 30, 21:44 UTC
   Update - We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
   
   Oct 30, 21:00 UTC
   Update - We are investigating elevated errors when viewing some Dependabot alerts.
   
   Oct 30, 20:59 UTC
   Investigating - We are investigating reports of impacted performance for some GitHub services.

4. 30 Oct · 21:44 UTC 🟡 Identified atom

   Oct 30, 21:44 UTC
   Update - We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
   
   Oct 30, 21:00 UTC
   Update - We are investigating elevated errors when viewing some Dependabot alerts.
   
   Oct 30, 20:59 UTC
   Investigating - We are investigating reports of impacted performance for some GitHub services.

5. 30 Oct · 21:00 UTC 🟡 Identified atom

   Oct 30, 21:00 UTC
   Update - We are investigating elevated errors when viewing some Dependabot alerts.
   
   Oct 30, 20:59 UTC
   Investigating - We are investigating reports of impacted performance for some GitHub services.