‹ Back to incident history

Disruption with Dependabot Alerts

ResolvedMinor incidentGitHub
Friday, October 23, 2026 22:58 – Saturday, October 24, 2026 02:51 (3 hr 52 min)
Updates
ResolvedSaturday, October 24, 2026 02:51

We identified that an advisory-publication driven fan-out was overwhelming Dependabot alert processing on repositories by saturating the queue with its own events, delaying processing of events related to repository pushes.<br /><br />We have now isolated this fan-out and applied a throttle so it runs at a fixed rate and cannot delay other events. This remediation has successfully prevented a new fan-out process impacting users.

MonitoringSaturday, October 24, 2026 02:36

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

InvestigatingSaturday, October 24, 2026 01:27

Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability. <br /><br />We're continuing to investigate and work to restore normal processing.

InvestigatingSaturday, October 24, 2026 00:43

We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring progress and will share another update as we learn more.

InvestigatingSaturday, October 24, 2026 00:11

We’re continuing to investigate delays in some Dependabot alerts closing after affected repositories are updated. Alert processing remains backed up, and additional processing capacity is rolling out to help reduce the backlog. We’re monitoring the rollout and will share another update as we learn more.

InvestigatingFriday, October 23, 2026 23:39

We’re scaling alert processing capacity to reduce the backlog causing delays in some Dependabot alerts closing after affected repositories have been updated. We’re continuing to monitor and will share another update as more information becomes available.

InvestigatingFriday, October 23, 2026 23:00

We’re investigating delays in some Dependabot alerts closing after affected repositories have been updated to address a vulnerability. Alert processing is backed up. We’ll share more information as it becomes available.

InvestigatingFriday, October 23, 2026 22:58

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