Skip to main content
Knock logo

Is Knock Down?

No — Knock is up

Reachable from all 8 checked regions

Average response time: 344ms

Last checked · checks run every 6 hours

Official status page: https://status.knock.app

Knock uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
280ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 13 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

13-day clean streak
Aug 22: no data
Aug 23: no data
Aug 24: no data
Aug 25: no data
Aug 26: no data
Aug 27: no data
Aug 28: no data
Aug 29: no data
Aug 30: no data
Aug 31: no data
Sep 1: no data
Sep 2: no data
Sep 3: no data
Sep 4: no data
Sep 5: no data
Sep 6: no data
Sep 7: no data
Sep 8: 100.00% uptime, 16 checks
Sep 9: 100.00% uptime, 24 checks
Sep 10: 100.00% uptime, 32 checks
Sep 11: 100.00% uptime, 32 checks
Sep 12: 100.00% uptime, 32 checks
Sep 13: 100.00% uptime, 32 checks
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 31 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 16 checks
Aug 22 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra
283ms
DNS 86ms TCP 1ms TLS 11ms TTFB 274ms
gru
395ms
DNS 191ms TCP 1ms TLS 8ms TTFB 384ms
iad
161ms
DNS 43ms TCP 1ms TLS 7ms TTFB 130ms
jnb
678ms
DNS 273ms TCP 0ms TLS 8ms TTFB 669ms
lax
204ms
DNS 43ms TCP 1ms TLS 9ms TTFB 193ms
lhr
468ms
DNS 145ms TCP 7ms TLS 9ms TTFB 371ms
nrt
267ms
DNS 17ms TCP 1ms TLS 8ms TTFB 257ms
ord
303ms
DNS 165ms TCP 3ms TLS 9ms TTFB 285ms

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 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

Twilio
Twilio
SendGrid (Twilio)
SendGrid (Twilio)
OneSignal
OneSignal
Resend
Resend

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.
  • 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. We only change the 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. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Knock goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required