Knock: Subscription workflows are delayed for some customers

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 46m it lasted.
Anything that failed between 2026-02-18 10:16 UTC and 2026-02-18 11:02 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.

investigatingFeb 18, 2026, 10:16 AM UTC
We're currently investigating an issue with subscriptions in our service.
provider
monitoringFeb 18, 2026, 10:32 AM UTC
Our service has caught up on the backlog of subscription workflow executions.
provider
resolvedFeb 18, 2026, 11:02 AM 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-02-18 11:02 UTC. For Knock's live state, see https://down.guide/knock.

How long did it last?

46m, from 2026-02-18 10:16 UTC to 2026-02-18 11:02 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.