ChangesKnockSockets service impaired
Knock: Incident updated: Sockets service impaired
Summary pending. The diff below shows exactly what changed.
Incident page: the full timeline of updates
What changed
Struck in red is what Knock 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-29 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
04463047f7260a7e…After captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8bb5c4b42df6bd4f…
History of this incident
Friday, October 30
3 incident changes
- Normal progressIncident
Incident updateSockets service impaired
- Normal progressIncident
Incident updateSockets service impaired
- Normal progressIncident
Incident updateSockets service impairedthis change
Thursday, October 29
1 incident change
- OutageMajor incident
Knock reported a major Sockets service impairment starting 2026-10-29 23:30 UTC: new connections to in-app feeds and guides via api.knock.app may fail. Normal API operations and notification delivery were unaffected. The incident remained open when archived, open for 0 min at the last update; Knock was investigating and working to restore service.
Cite this
Incident updated: Sockets service impaired on Knock’s status page, changed 2026-10-30 00:03 UTC (change 2 of 4).
- Title
- Incident updated: Sockets service impaired
- Vendor
- Knock
- Date
- URL
- https://rewindex.com/change/r6dde4cb188bf18