Live / GitHub / Incident
GitHub: Disruption with Dependabot Alerts
GitHub · github.comMinor incidentResolved2026-10-23 18:51 UTC
Public — what happened
Summary
GitHub said it began investigating a minor disruption on October 23, 2026 at 14:58 UTC, in which some Dependabot alerts were slow to close after repositories were updated to fix a vulnerability. The company said alert processing was backed up, and it added processing capacity over the next few hours to work through the backlog. GitHub reported the problem as mitigated at 18:36 UTC and marked it resolved at 18:51 UTC after monitoring for stability. It did not state a cause in its updates.
Timeline
- Started — 2026-10-23 14:58 UTC
- Investigating — 2026-10-23 14:58 UTC (6 updates)
- Monitoring — 2026-10-23 18:36 UTC
- Resolved — 2026-10-23 18:51 UTC · 3h 53m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach GitHub against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for GitHub: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the GitHub report →
More from GitHub
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.