GitHub outage on October 23, 2026: Disruption with Dependabot Alerts

GitHub has reported an incident affecting GitHub since 14:58 UTC on 23 October 2026 (3 hours 49 minutes so far).

github.com All times UTC

Open

Official incident reported by GitHub

Started: 14:58; 23 Oct 2026 UTC
Status: Open; not resolved yet
Duration: 3h 49m; 3 hours 49 minutes so far
Impact: Minor; as rated by GitHub
Updates: 7; posted by GitHub

Timeline

All times UTC.

Official incident from GitHub

Disruption with Dependabot Alerts

Monitoring Minor impact 23 Oct 2026 14:58 UTC View on GitHub's status page

14:58 Official
Investigating
We are investigating reports of impacted performance for some GitHub services.
15:00 Official
Investigating
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.
15:39 Official
Investigating
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.
16:11 Official
Investigating
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.
16:43 Official
Investigating
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.
17:27 Official
Investigating
Some Dependabot alerts continue to be delayed in closing after repository updates address a vulnerability. We're continuing to investigate and work to restore normal processing.
18:36 Official
Monitoring
The degradation has been mitigated. We are monitoring to ensure stability.

"Official" rows are quoted from GitHub's public status page, www.githubstatus.com. Very long posts are shortened.

What our checkpoints saw

HostTracker's checkpoints, which test github.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live GitHub status shows what our checks see right now.

All GitHub incidents Live GitHub status Every service we track

Does your product depend on GitHub?

An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.

You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.

Start monitoring free Check another address

Independent measurement by HostTracker. Not affiliated with GitHub. Official updates are quoted from GitHub's public status page and remain GitHub's own words.