Knock: Elevated errors connecting to the Knock V1 Websocket API

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 49m it lasted.
Anything that failed between 2026-06-16 17:55 UTC and 2026-06-16 18:44 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.

investigatingJun 16, 2026, 5:55 PM UTC
We're currently investigating elevated error rates connecting to the V1 Websocket API. Realtime behavior for in-app feed and guides is degraded as a result.
provider
monitoringJun 16, 2026, 6:26 PM UTC
We have shipped a fix and are seeing resolution in websocket connections. We are continuing to monitor closely.
provider
resolvedJun 16, 2026, 6:44 PM UTC
This incident has been resolved.
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-06-16 18:44 UTC. For Knock's live state, see https://down.guide/knock.

How long did it last?

49m, from 2026-06-16 17:55 UTC to 2026-06-16 18:44 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.