Knock: Broadcast delays
Affected components: Notification delivery
Timeline of updates
- investigating
We're currently investigating an issue with broadcast messages being dispatched for a subset of customers. We'll have an update soon.
- identified
We've identified the issue with the service and are actively working on a fix.
- monitoring
A fix has been implemented. We've processed through our broadcast backlog and are monitoring.
Changes Rewindex caught on this incident
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-11-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
8da2275a64e85da3…Version 2 captured
In the 2026-11-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
93caa40d23b1a045…Version 3 captured
In the 2026-11-20 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
dc82d372fcd43435…
Impact, status and times are the vendor’s own, as last archived. View on status.knock.app (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Knock, started 2026-11-20 22:16 UTC, not resolved, 3 update(s); edited after publishing.
- Title
- Broadcast delays
- Vendor
- Knock
- Date
- URL
- https://rewindex.com/company/knock/incidents/01M7XGHHV7SWSV6QBNEE2KFTR3
Knock profileRecent Knock incidentsAll outages on November 20, 2026Knock in November 2026MarkdownJSON