Knock: We're seeing some delays in log processing

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-03-03 17:02 UTC and 2026-03-03 17:32 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.

investigatingMar 3, 2026, 5:02 PM UTC
We're currently investigating an issue with log processing. There are no issues currently processing workflows and messages, but logs are affected.
provider
identifiedMar 3, 2026, 5:23 PM UTC
We've identified the issue with the service and are actively working on a fix.
provider
monitoringMar 3, 2026, 5:24 PM UTC
A fix has been implemented, and we're currently monitoring the service.
provider
resolvedMar 3, 2026, 5:32 PM UTC
This incident has now been resolved and the service is now fully operational.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Knock still down?

No, this incident was resolved 2026-03-03 17:32 UTC. For Knock's live state, see https://down.guide/knock.

How long did it last?

29m, from 2026-03-03 17:02 UTC to 2026-03-03 17:32 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.