outages.live
Live
KnockIncident ·

Warehouse message synchronization delayed

ResolvedOfficial update

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

The latest update from Knock.

State

Resolved

Started

Lasted

30 h 56 min

Worst impact

Partial outage

Timeline

5 updates
14:0921:5305:3713:2121:05
Partial outageUpdate postedTimes in UTC

Identified

14 h 7 min 46%

Monitoring

16 h 49 min 54%

Updates

Times in UTC

As posted by Knock

Resolved

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

Monitoring

We have successfully rebuilt the tables for export and are running syncs now. We are continuing to monitor and will be working on some remediation and further stabilization in the coming days.

Identified

We're actively working on getting the most up-to-date message data for export. The job is taking an extended time to run. We are going to re-run syncs as soon as this job has completed.

Identified

We're actively re-syncing current message data into the data warehouse and expect this to complete in the next 3 hours. At that time, we will issue a new sync to all downstream destinations with up to date data.

Identified

Message synchronization into customer data warehouses is delayed. We are working on resolving the delay. Other data synchronization is not affected.

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

19× 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·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

Knock·Workflow processing and message delivery errors

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

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.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