Knock: Elevated response times loading some log data

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 32m it lasted.
Anything that failed between 2026-06-04 11:40 UTC and 2026-06-04 12:11 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 4, 2026, 11:40 AM UTC
We're seeing elevated response times loading some log data. This is leading to slower page loads in the Dashboard and slower responses from some V1 API endpoints.
provider
monitoringJun 4, 2026, 12:07 PM UTC
We have shipped a fix and we are seeing recovery of log data load times. We are continuing to monitor closely before resolving.
provider
resolvedJun 4, 2026, 12:11 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-04 12:11 UTC. For Knock's live state, see https://down.guide/knock.

How long did it last?

32m, from 2026-06-04 11:40 UTC to 2026-06-04 12:11 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.