outages.live
Live
KnockIncident ·

Workflow processing and message delivery errors

ResolvedOfficial update

This incident has now been resolved and the service is now fully operational.

The latest update from Knock.

State

Resolved

Started

Lasted

1 h 45 min

Worst impact

Partial outage

Timeline

4 updates
16:4217:0817:3418:0018:26
Partial outageUpdate postedTimes in UTC

Identified

17 min 16%

Monitoring

1 h 28 min 84%

Updates

Times in UTC

As posted by Knock

Resolved

This incident has now been resolved and the service is now fully operational.

Monitoring

A fix has been implemented, and we're currently monitoring the service.

Monitoring

A fix has been implemented, and we're currently monitoring the service. Earlier failing workflows are being retried.

Identified

Some customers may seen errors in workflow run processing. We've identified the issue and are rolling out a fix.

Knock in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

4

Days with an incident

6

Median duration

1 h 39 min

This incident

About 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 39 min
90 days agoToday

Other Knock incidents

All incidents

Knock·Sockets service impaired

This incident has now been resolved and the service is now fully operational.

Resolved

Knock·Warehouse message synchronization delayed

We're back to normal sync schedules for our data warehouse connector.

Resolved

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.

Resolved

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.cc/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.cc/feed.xml?providers=knock
Slack
/feed subscribe https://outages.cc/feed.xml?providers=knock

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane