GitHub: Incident with Dependabot
Timeline of updates
- investigating
We are investigating reports of impacted performance for some GitHub services.
- investigating
We are investigating elevated errors when viewing some Dependabot alerts.
- investigating
We are continuing to investigate elevated errors when viewing some Dependabot alerts. We’ll provide more updates as we learn more.
- investigating
We have mitigated impact and are seeing recovery. We are monitoring for full recovery.
- monitoring
The degradation has been mitigated. We are monitoring to ensure stability.
- resolved
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.
Changes Rewindex caught on this incident
- Incident updated: Incident with Dependabot
- Incident updated: Incident with Dependabot
- Incident updated: Incident with Dependabot
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
484c88f2838a21f1…Version 2 captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8ea5330475db4392…Version 3 captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a0d9ea7685caa9fc…Version 4 captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
992b296c16f75cc1…
Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).