Minor incident

GitHub: Incident with Dependabot

Current status of GitHub: Operational — live GitHub status

Timeline

1. Oct 30, 2026, 20:59 UTC
   investigating
   We are investigating reports of impacted performance for some GitHub services.
2. Oct 30, 2026, 21:00 UTC
   investigating
   We are investigating elevated errors when viewing some Dependabot alerts.
3. Oct 30, 2026, 21:44 UTC
   investigating
   We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
4. Oct 30, 2026, 22:32 UTC
   investigating
   We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
5. Oct 30, 2026, 22:32 UTC
   monitoring
   The degradation has been mitigated. We are monitoring to ensure stability.
6. Oct 30, 2026, 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.

Updates as published by GitHub (original).