Message event delays

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 7m it lasted.

  Anything that failed between 2026-03-25 15:29 UTC and 2026-03-25 16:36 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

1. investigatingMar 25, 2026, 3:29 PM UTC

   We are investigating delays in creating and processing message events. Some customers may experience delays seeing message events in the Knock Dashboard. Some customers may also experience delays in outbound webhook events triggered by message events.

   provider

2. identifiedMar 25, 2026, 4:21 PM UTC

   We've implemented a fix and are seeing message event lag begin to recover.

   provider

3. identifiedMar 25, 2026, 4:22 PM UTC

   Webhook delivery lag has resolved. We are still waiting for message event Dashboard availability lag to recover.

   provider

4. resolvedMar 25, 2026, 4:36 PM UTC

   All message event lag has recovered. We are considering this incident resolved.

   provider

Corrections

None so far.

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