Broadcast delays
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 updatesInvestigating
13 min 1%
Identified
6 min 0%
Monitoring
30 h 15 min 99%
Updates
Times in UTCAs posted by Knock
A fix has been implemented. We've processed through our broadcast backlog and are monitoring.
We've identified the issue with the service and are actively working on a fix.
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 historyIncidents in 90 days
6
Days with an incident
10
Median duration
1 h 45 min
This incident
18× the median
Other Knock incidents
All incidentsKnock·Dashboard transactional email outage
Knock dashboard transactional emails were not delivered. Account invites were also degraded. Knock reports the incident is resolved. The outage lasted about 2 hours and 21 minutes.
Knock·Sockets service impaired
This incident has now been resolved and the service is now fully operational.
Knock·Warehouse message synchronization delayed
We're back to normal sync schedules for our data warehouse connector.
Knock·Knock dashboard login magic links are unavailable
This incident is resolved, and magic link login is fully functional. Malicious activity caused our email provider to flag the Knock dashboard's transactional emails, disrupting magic link deliverability. We've blocked the activity and restored email delivery. Only Knock's emails from hello@notify.knock.app were impacted. Customer email channels were unaffected.
Knock·Workflow processing and message delivery errors
This incident has now been resolved and the service is now fully operational.
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.
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.
https://outages.live/feed.xml?providers=knock/feed subscribe https://outages.live/feed.xml?providers=knockFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane