Workflow engine outage

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

  Anything that failed between 2026-07-10 15:17 UTC and 2026-07-10 15:40 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. investigatingJul 10, 2026, 3:17 PM UTC

   We're currently investigating an issue with our service. We'll have an update soon.

   provider

2. identifiedJul 10, 2026, 3:28 PM UTC

   We've identified the issue with the service and are actively working on a fix. We're seeing workflows and message deliveries process again at the usual rate.

   provider

3. monitoringJul 10, 2026, 3:33 PM UTC

   A fix has been implemented, and we're currently monitoring the service. All our services seem to be recovering. We're in the process of replaying any failed work that happened during the window. We expect there was no loss of workflows during this incident, but some work may have been delayed.

   provider

4. resolvedJul 10, 2026, 3:40 PM UTC

   This incident has now been resolved and the service is now fully operational. We're replaying any jobs that may have failed during the window. All our processing queues are fully caught up. We will share a full post mortem as soon as possible.

   provider

Corrections

None so far.

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