Is Knock Down?

No — Knock is up

Knock's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 338 ms

Right now

The verdict is the worse of these two. How we decide

Knock's status page

status.knock.app · read 3 minutes ago · checked every 3 minutes

Operational

Knock's components, as its status page reports them
Component	Status
API	Operational
Notification delivery	Operational
In-app feeds and guides	Operational
Dashboard	Operational
Webhook delivery	Operational
Logs	Operational
Link and open tracking	Operational
Data warehouse synchronization	Operational
Agent	Operational

Open their status page

FlareWarden checks

knock.app from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 338 ms
Checked: 5 hours ago

By region

Ashburn reachable, 251 ms
Dallas reachable, 328 ms
Frankfurt reachable, 339 ms
Johannesburg reachable, 560 ms
London reachable, 270 ms
Los Angeles reachable, 320 ms
Newark reachable, 284 ms
São Paulo reachable, 352 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	143 ms	1 ms	16 ms	247 ms
Dallas	143 ms	1 ms	10 ms	324 ms
Frankfurt	110 ms	2 ms	13 ms	331 ms
Johannesburg	219 ms	1 ms	7 ms	557 ms
London	19 ms	4 ms	13 ms	255 ms
Los Angeles	100 ms	2 ms	12 ms	314 ms
Newark	165 ms	4 ms	12 ms	277 ms
São Paulo	139 ms	2 ms	13 ms	347 ms

We check that knock.app loads, not every feature behind it. Test it yourself

History

Incidents Knock reported

Since Oct 22, 15 days · from status.knock.app

Incidents: 1
Major or critical: 1
Median to resolve: 1h 34m

Sockets service impaired
major · Oct 29
lasted 1h 34m

Knock website availability

Measured by FlareWarden · knock.app

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 339ms

Last 30 days

59-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of knock.app from multiple regions every 6 hours. Knock's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 59 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Knock does

Knock is notification infrastructure that applications send events to, letting it decide which users to notify, on which channels, and with what batching and preference rules. It delivers over email, push, SMS, chat and in-app feeds through providers the customer configures, so a product team writes one integration instead of one per channel.

What an outage looks like

Notifications stop reaching users while the application that triggered them reports success, because Knock accepted the event and delivery is what failed. In-app notification feeds render empty or stop updating in real time. Webhook and link tracking data goes missing, and the dashboard may be unreachable while delivery itself continues normally.

What to do about it

Read status.knock.app, which publishes per-component uptime for API, Notification delivery, In-app feeds and guides, Dashboard, Webhook delivery, Logs, Link and open tracking, Data warehouse synchronization and Agent. Match the symptom to the row. If Notification delivery is affected while API is healthy, your events were accepted and the work is queued rather than lost, so avoid re-triggering them and creating duplicates for every recipient.

Is it down for everyone, or just you?

If this page says Knock is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Knock outage FAQ

My app says the notification was sent but nobody received it. Is Knock down?

That is the shape of a Notification delivery incident. Knock reports API separately from Notification delivery, so it can accept your event and return success while the message never reaches the channel provider. Your application sees no error because the send succeeded from its point of view. Check the Notification delivery row on status.knock.app before investigating your workflow.

The in-app feed is empty but emails are arriving. Is that a Knock outage?

It can be. Knock publishes In-app feeds and guides as a component separate from Notification delivery, so the embedded feed can fail while email, push and SMS continue normally. Users then see an empty notification bell while getting messages elsewhere, which reads as lost notifications and is not. Check that specific row rather than assuming everything has stopped.

Will notifications queued during an outage be delivered later?

Events accepted by the API are recorded, so a delivery incident usually means delayed rather than dropped notifications. Knock does not publish a guarantee covering every failure mode, so confirm against the incident's updates and the Logs component once it clears. Avoid re-triggering workflows during the window, because the queued copy and the new one will both deliver.

Is a Knock outage the same as my email or SMS provider being down?

No, and separating them matters. Knock delivers through providers you configure, so a fault at your email or SMS vendor stops messages on that channel while Knock reports healthy. status.knock.app covers Knock's own components. If Knock is all-clear and only one channel is failing, check that provider's status page instead.

The Knock dashboard is down. Are notifications still going out?

Usually yes. Dashboard is its own component, separate from API and Notification delivery, so you can lose the interface for editing workflows and inspecting messages while delivery continues. Treat it as lost visibility rather than lost delivery, and avoid publishing workflow changes you cannot preview or verify until it recovers.

How we measure this

We request Knock's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Knock publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Knock itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Knock goes down

We check Knock every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required