- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 18of 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 1h 12m it lasted.
Anything that failed between 2026-03-31 13:06 UTC and 2026-03-31 14: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 4
- investigating
We're currently investigating an issue with delayed ingestion of our API logs, putting pressure on our ingestion pipeline and resulting in some degraded state for browsing API logs as well.
provider
- monitoring
We’ve shipped a fix and we’re seeing initial signs of recovery. We are continuing to monitor closely.
provider
- monitoring
We are seeing full recovery of API log delays. We are continuing to monitor before closing out this incident
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-3dd075b1a0
Is Knock still down?
No, this incident was resolved 2026-03-31 14:18 UTC. For Knock's live state, see https://down.guide/knock.
How long did it last?
1h 12m, from 2026-03-31 13:06 UTC to 2026-03-31 14: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.