‹ Back to incident history

Incident with Dependabot

ResolvedMinor incidentGitHub
Saturday, October 31, 2026 04:59 – Saturday, October 31, 2026 07:29 (2 hr 29 min)
Updates
ResolvedSaturday, October 31, 2026 07:29

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.

MonitoringSaturday, October 31, 2026 06:32

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

InvestigatingSaturday, October 31, 2026 06:32

We have mitigated impact and are seeing recovery. We are monitoring for full recovery.

InvestigatingSaturday, October 31, 2026 05:44

We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.

InvestigatingSaturday, October 31, 2026 05:00

We are investigating elevated errors when viewing some Dependabot alerts.

InvestigatingSaturday, October 31, 2026 04:59

We are investigating reports of impacted performance for some GitHub services.

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