- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 33of 100
What to do
Check whether your product depends on Knock. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1d 2h it lasted.
Anything that failed between 2026-07-01 21:53 UTC and 2026-07-03 00:12 UTC may need a replay.Subscribe to Knock's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=knock works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Knock 2
- monitoring
Message data synchronization into downstream customer data warehouse destinations is delayed for messages created after 8 PM ET on June 30, 2026. We have implemented a fix. We expect the issue to be fully resolved following the nightly synchronization job scheduled on July 2nd, 2026.
provider
- resolved
This incident has now been resolved and the service is now fully operational.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-cf71a134e3
Is Knock still down?
No, this incident was resolved 2026-07-03 00:12 UTC. For Knock's live state, see https://down.guide/knock.
How long did it last?
1d 2h, from 2026-07-01 21:53 UTC to 2026-07-03 00:12 UTC, by the times Knock posted.
What caused it?
Knock hasn't published a root cause. If it does, it shows here.
Where does this come from?
Knock's official status page, https://status.knock.app, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.