ChangesGitHubIncident with Webhooks
GitHub: Critical incident: Incident with Webhooks
Summary pending. The diff below shows exactly what changed.
Discussed on Hacker News
- 81 points · 61 comments · posted · posted 6 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.
First version of this incident archived by Rewindex. 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 this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
After captured
In the 2026-11-11 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
fac7b8be7789c336…
History of this incident
TodayFriday, November 20Fri, Nov 20
1 rewrite
- EditedEdited by the vendor
Wednesday, November 11
4 incident changes
- Normal progressIncident
- Normal progressIncident
- Normal progressIncident
- DegradationCritical incident
Incident with Webhooksthis change
Cite this
Critical incident: Incident with Webhooks on GitHub’s status page, changed 2026-11-11 20:48 UTC (change 1 of 5).
- Title
- Critical incident: Incident with Webhooks
- Vendor
- GitHub
- Date
- URL
- https://rewindex.com/change/id0ecc42aafbca6