User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
Is Knock down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → knock.app—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 24 min ago. Last stored result reached it in 230 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 189 ms | 0 |
| Mon 20 | 0 | 0.0 | 194 ms | 0 |
| Mon 22 | 0 | 0.0 | 189 ms | 0 |
| Tue 00 | 0 | 0.0 | 230 ms | 0 |
| Tue 02 | 0 | 0.0 | 263 ms | 0 |
| Tue 04 | 0 | 0.0 | 253 ms | 0 |
| Tue 07 | 0 | 0.0 | 244 ms | 0 |
| Tue 09 | 0 | 0.0 | 135 ms | 0 |
| Tue 11 | 0 | 0.0 | 197 ms | 0 |
| Tue 13 | 0 | 0.0 | 180 ms | 0 |
| Tue 15 | 0 | 0.0 | 253 ms | 0 |
| Tue 17 | 0 | 0.0 | 157 ms | 0 |
| Tue 20 | 0 | 0.0 | 241 ms | 0 |
| Tue 22 | 0 | 0.0 | 118 ms | 0 |
| Wed 00 | 0 | 0.0 | 158 ms | 0 |
| Wed 02 | 0 | 0.0 | 215 ms | 0 |
| Wed 05 | 0 | 0.0 | 229 ms | 0 |
| Wed 07 | 0 | 0.0 | 194 ms | 0 |
| Wed 09 | 0 | 0.0 | 181 ms | 0 |
| Wed 12 | 0 | 0.0 | 222 ms | 0 |
| Wed 14 | 0 | 0.0 | 224 ms | 0 |
| Wed 16 | 0 | 0.0 | 306 ms | 0 |
| Wed 18 | 0 | 0.0 | 218 ms | 0 |
| Wed 20 | 0 | 0.0 | 176 ms | 0 |
| Wed 22 | 0 | 0.0 | 161 ms | 0 |
| Thu 00 | 0 | 0.0 | 217 ms | 0 |
| Thu 03 | 0 | 0.0 | 141 ms | 0 |
| Thu 05 | 0 | 0.0 | 202 ms | 0 |
| Thu 07 | 0 | 0.0 | 245 ms | 0 |
| Thu 09 | 0 | 0.0 | 209 ms | 0 |
| Thu 11 | 0 | 0.0 | 275 ms | 0 |
| Thu 13 | 0 | 0.0 | 153 ms | 0 |
| Thu 15 | 0 | 0.0 | 196 ms | 0 |
| Thu 17 | 0 | 0.0 | 193 ms | 0 |
| Thu 19 | 0 | 0.0 | 224 ms | 0 |
| Thu 21 | 0 | 0.0 | 218 ms | 0 |
| Thu 23 | 0 | 0.0 | 218 ms | 0 |
| Fri 01 | 0 | 0.0 | 208 ms | 0 |
| Fri 02 | 0 | 0.0 | 170 ms | 0 |
| Fri 04 | 0 | 0.0 | 212 ms | 0 |
| Fri 06 | 0 | 0.0 | 178 ms | 0 |
| Fri 08 | 0 | 0.0 | 209 ms | 0 |
| Fri 10 | 0 | 0.0 | 200 ms | 0 |
| Fri 11 | 0 | 0.0 | 146 ms | 0 |
| Fri 13 | 0 | 0.0 | 257 ms | 0 |
| Fri 15 | 0 | 0.0 | 254 ms | 0 |
| Fri 17 | 0 | 0.0 | 230 ms | 0 |
| Fri 18 | 0 | 0.0 | 182 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Knock badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Knock yet. Outages of 10 minutes or more get their own page here.
Having trouble with Knock?
One report per service every 10 minutes from this network. No account.
Follow Knock
Get an email when Knock goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Knock alerts to Slack, Discord or a webhook — free.
About Knock
Knock is listed in our Cloud & developer category and checked at knock.app. Knock is agentic customer engagement infrastructure to grow faster. Ship cross-channel lifecycle and transactional messaging from your favorite agent.
Knock publishes an official status page at status.knock.app; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 208 ms average, 146–257 ms range across 14 successful checks.
Questions
Is Knock down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Knock last down?
We have not recorded a public Knock incident since monitoring began 8 days ago.
What is Knock's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Knock respond?
208 ms on average over the last 24 hours (146–257 ms).
Does Knock have an official status page?
Yes, at https://status.knock.app.
Knock not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Knock here at once, the problem is on Knock's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Knock. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.