ChangesGitHubDisruption with GitHub services
GitHub: Incident updated: Disruption with GitHub services
Summary pending. The diff below shows exactly what changed.
Discussed on Hacker News
- 13 points · 2 comments · posted · posted 4 min after the vendor’s first update
Threads are matched automatically by vendor name and timing; points and comments refresh every 30 minutes. Method and limits.
Incident page: the full timeline of updates
What changed
Struck in red is what GitHub removed; blue is what they added. Muted text is unchanged context.
Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).
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.
Before captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
20ecf0f694b24445…After captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
a8a37804b76f378c…
History of this incident
YesterdayFriday, October 30Fri, Oct 30
4 incident changes
- Normal progressIncident
Incident updateDisruption with GitHub services
- Normal progressIncident
Incident updateDisruption with GitHub servicesthis change
- Normal progressIncident
Incident updateDisruption with GitHub services
- DegradationCritical incident
Disruption with GitHub services
GitHub reported minor performance degradation affecting some GitHub services starting at 2026-10-30 14:31 UTC. The incident was under investigation and still open when archived, with 0 min elapsed at the last update; no specific services, cause or fix were stated.