Live

Broadcast delays

0

Broadcast message delivery is delayed for a subset of Knock customers. Knock implemented a fix and processed the broadcast backlog. Knock is now monitoring the service.

State

Monitoring

Started

Ongoing for

30 h 34 min

Worst impact

Degraded

Timeline

3 updates
22:1605:5513:3421:1204:51
DegradedUpdate postedTimes in UTC

Investigating

13 min 1%

Identified

6 min 0%

Monitoring

30 h 15 min 99%

Updates

Times in UTC

As posted by Knock

Monitoring

A fix has been implemented. We've processed through our broadcast backlog and are monitoring.

Identified

We've identified the issue with the service and are actively working on a fix.

Investigating

We're currently investigating an issue with broadcast messages being dispatched for a subset of customers. We'll have an update soon.

Knock in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

6

Days with an incident

10

Median duration

1 h 45 min

This incident

18× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

30 h 56 min
median 1 h 45 min
90 days agoToday

Other Knock incidents

All incidents

Follow Knock

Your coding agent knows when Knock is down, and tells you when a failure is theirs, not yours. You can also get Knock incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "knock" and tell me if Knock has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=knock
Slack
/feed subscribe https://outages.live/feed.xml?providers=knock

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane