outages.live
Live

Knock

Knock is operational

Checked Operational

User reports

What people told outages.live in the last 24 hours, reviewed before it shows. Not from the Knock status page.

No reviewed reports in the last 24 hours.

History

90 days agoToday

outages.live tracks Knock since . The days before that show only what Knock published.

Incidents in 90 days

4

Days with an incident

6

Median duration

1 h 39 min

Longest incident

30 h 56 min

Components

9
API Operational
90 days agoNo incidentsToday
Notification delivery Operational
90 days agoNo incidentsToday
In-app feeds and guides Operational
90 days agoNo incidentsToday
Dashboard Operational
90 days agoNo incidentsToday
Webhook delivery Operational
90 days agoNo incidentsToday
Logs Operational
90 days agoNo incidentsToday
Link and open tracking Operational
90 days agoNo incidentsToday
Data warehouse synchronization Operational
90 days agoNo incidentsToday
Agent Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 29, 2026

Duration1 h 34 min to Sockets service impairedPartial outage

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

Oct 1, 2026

Duration30 h 56 min to Warehouse message synchronization delayedPartial outage

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

Sep 21, 2026

Duration1 h 3 min to Knock dashboard login magic links are unavailablePartial outage

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.

Aug 31, 2026

Duration1 h 45 min to Workflow processing and message delivery errorsPartial outage

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.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane