GitHub incident

Disruption with Dependabot Alerts

Resolved after 3 hours 52 minutes, on October 23, 2026.

resolved Oct 23, 2026, 06:51 PM UTC

This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Started
Oct 23, 2026, 02:58 PM UTC
Resolved
Oct 23, 2026, 06:51 PM UTC
Duration
3h 52m
Detected by Pingoru
Oct 23, 2026, 02:58 PM UTC

Update timeline

  1. investigating Oct 23, 2026, 02:58 PM UTC

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

  2. investigating Oct 23, 2026, 03:00 PM UTC

    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.

  3. investigating Oct 23, 2026, 03:39 PM UTC

    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.

  4. investigating Oct 23, 2026, 04:11 PM UTC

    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.

  5. investigating Oct 23, 2026, 04:43 PM UTC

    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.

  6. investigating Oct 23, 2026, 05:27 PM UTC

    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.

  7. monitoring Oct 23, 2026, 06:36 PM UTC

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

  8. resolved Oct 23, 2026, 06:51 PM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Your product runs on more than GitHub

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →