Knock logo

Is Knock Down?

CommunicationLive status, outages, and incident history

No. Knock is up right now.

Every monitored Knock system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 4m agoLive · every 60s

Know the moment Knock breaks

Knock is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Knock status page
How we know: the official Knock status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Knock Status Summary

As of 17:52 UTC on 14 November 2026, Knock is operational. PulsAPI checked Knock's official status page and found 9 of 9 components operational, with no active incidents. The latest incident, "Dashboard transactional email outage", was on Nov 6, 2026 and lasted 2h 20m.

Cite as: PulsAPI, “Knock status”, checked 14 November 2026, 17:52 UTC. https://www.pulsapi.com/services/knock

Knock Component Status

The main Knock systems on this page. All 9 are operational right now.

9operational
Agent
Operational
API
Operational
Dashboard
Operational

6 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Data warehouse synchronization, In-app feeds and guides, Link and open tracking, Logs, Notification delivery, Webhook delivery.

See all of them free

Component statuses may change independently during partial outages.

Recent Knock Outages & Incidents

Incident history from the official Knock status page, including resolution updates.

Dashboard transactional email outageResolved Nov 6, 2026 · 2h 20mResolved

This incident has now been resolved and the service is now fully operational. --- [2026-11-06T13:46:00Z] (monitoring) A fix has been implemented, and we're currently monitoring the service. --- [2026-11-06T13:10:32Z] (identified) We're still working on a fix to all transactional emails and mitigating the ongoing spam issue we're dealing with. For the time being, account invites are degraded and are still not sending. --- [2026-11-06T12:42:34Z] (identified) We've identified the source of the issue with our transactional email provider (Postmark) and are implementing a fix. --- [2026-11-06T12:27:04Z] (investigating) We're investigating reports that transactional emails from the Knock dashboard are not being delivered. We're actively working with our mail provider on a fix.

Sockets service impairedResolved Oct 29, 2026 · 1h 34mResolved

This incident has now been resolved and the service is now fully operational. --- [2026-10-30T00:38:20Z] (monitoring) A fix has been implemented, and we're currently monitoring the service. --- [2026-10-30T00:01:56Z] (identified) We've identified the issue with the service and are actively working on a fix. --- [2026-10-29T23:30:15Z] (investigating) New connections to in-app feeds and guides may be failing when connecting to api.knock.app. We are investigating and working on restoring service. Normal API operations and notification delivery remain unaffected.

Warehouse message synchronization delayedResolved Oct 1, 2026 · 30h 55mResolved

We're back to normal sync schedules for our data warehouse connector. --- [2026-10-02T04:16:29Z] (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. --- [2026-10-02T02:56:55Z] (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. --- [2026-10-01T16:06:46Z] (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. --- [2026-10-01T14:09:24Z] (identified) Message synchronization into customer data warehouses is delayed. We are working on resolving the delay. Other data synchronization is not affected.

Knock Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Knock incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% averageNov 14

Live Knock Outage Reports

Problems reported by engineers using Knock. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Knock problems reported yet.

Something wrong with Knock on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Knock

Knock's status page at status.knock.app lists 9 components, such as API, Agent and Dashboard. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Knock's side or yours.

Knock Status FAQ

Is Knock down right now?

The verdict at the top of this page comes from the latest poll of the official Knock status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Knock is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Knock recovers.

How do I check Knock uptime history?

PulsAPI tracks Knock uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Knock changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Knock outages?

PulsAPI reads the official Knock status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Knock components?

Yes. PulsAPI monitors 9 individual Knock components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Knock goes down?

Yes. Create a free account and subscribe to Knock: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Knock to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Knock problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Knock?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Knock plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Knock with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services