Disruption with Dependabot Alerts
Oct 23, 14:58 UTCOct 23, 18:51 UTC
Duration
3h 53m
Impact
Minor
Root cause
Not disclosed
GitHub, 90 days
63 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Oct 23, 18:51 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.
- Monitoring · Oct 23, 18:36 UTC
The degradation has been mitigated. We are monitoring to ensure stability.
- Investigating · Oct 23, 17:27 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.
- Investigating · Oct 23, 16:43 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.
- Investigating · Oct 23, 16:11 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.
- Investigating · Oct 23, 15:39 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.
- Investigating · Oct 23, 15:00 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.
- Investigating · Oct 23, 14:58 UTC
We are investigating reports of impacted performance for some GitHub services.
More from GitHub
Full historyGrok 4.6 and Grok 4.7 Service Issueslasted 42mDelayed Actions status check resultslasted 36mProject updates delayedlasted 11h 2mIncident with Actions Resultslasted 1h 1mDelays for Pull Requests and Webhook deliverieslasted 4h 30mDegraded availability for GitHub Actions, GitHub Pages and Webhookslasted 1h 8m