GitHub reported this minor-impact incident on its official status page on Oct 30, 2026, 20:59 UTC. It was resolved after 2h 30m.
Right now GitHub is operational. Live GitHub status →
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.<br /><br />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.
The degradation has been mitigated. We are monitoring to ensure stability.
We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
We are investigating elevated errors when viewing some Dependabot alerts.
We are investigating reports of impacted performance for some GitHub services.
Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
GitHub reported 67 incidents in the last 90 days, 24 of them major or critical. A typical incident lasted 1h 15m. See GitHub's uptime and incident history