- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 16of 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 29m it lasted.
Anything that failed between 2026-02-10 00:50 UTC and 2026-02-10 01:20 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 4
- investigating
We're currently investigating an issue with delayed workflow run logs. Workflow execution and message delivery are unaffected, but our log queues are currently behind.
provider
- identified
We’ve shipped a fix to improve throughput for our consumer that processes workflow run logs and are beginning to see the consumer catch up on its backlog. We’re continuing to monitor closely.
provider
- monitoring
Workflow run logs are no longer delayed. We are monitoring closely before closing this out.
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-079c2cf12d
Is Knock still down?
No, this incident was resolved 2026-02-10 01:20 UTC. For Knock's live state, see https://down.guide/knock.
How long did it last?
29m, from 2026-02-10 00:50 UTC to 2026-02-10 01:20 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.