- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 20of 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 2h 59m it lasted.
Anything that failed between 2026-05-01 10:19 UTC and 2026-05-01 13:18 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 7
- investigating
We're currently investigating an issue related to slow notification processing and message delivery. Some workflows will be delayed
provider
- investigating
We're seeing an extremely high amount of load on our services which is causing workflow and broadcast delays. We're working to relieve the pressure immediately.
provider
- investigating
We're seeing some recovery on our services but are dealing with delays in some workflow and broadcast processing still. Our logging service is also currently delayed, so may not reflect the latest as we catch up and work through a huge influx of work.
provider
- identified
One of our workflow queues is currently still backlogged, but we're seeing good resolution across other areas of our service and we have effectively cordoned off the source of the issue. We're burning through remaining work and are exploring ways to shed the load further to get back to stability.
provider
- identified
We've taken steps to shuffle around work in our system which has meant that we're processing new work for all customers again. We still have some queued workflow executions that we're working through and expect to be fully caught up in the next 40 minutes.
provider
- identified
We are seeing a recovery in all workflow and broadcast processing delays. We are monitoring closely.
provider
- resolved
All behavior remains normal, we are considering this incident resolved.
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-be59444a06
Is Knock still down?
No, this incident was resolved 2026-05-01 13:18 UTC. For Knock's live state, see https://down.guide/knock.
How long did it last?
2h 59m, from 2026-05-01 10:19 UTC to 2026-05-01 13:18 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.