User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Smart home
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 2 hr ago. Last stored result reached it in 749 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 627 ms | 0 |
| Nov 7 | 0 | 0.0 | 547 ms | 0 |
| Nov 7 | 0 | 0.0 | 584 ms | 0 |
| Nov 7 | 0 | 0.0 | 655 ms | 0 |
| Nov 7 | 0 | 0.0 | 479 ms | 0 |
| Nov 8 | 0 | 0.0 | 624 ms | 0 |
| Nov 8 | 0 | 0.0 | 648 ms | 0 |
| Nov 8 | 0 | 0.0 | 597 ms | 0 |
| Nov 8 | 0 | 0.0 | 696 ms | 0 |
| Nov 9 | 0 | 0.0 | 623 ms | 0 |
| Nov 9 | 0 | 0.0 | 613 ms | 0 |
| Nov 9 | 0 | 0.0 | 596 ms | 0 |
| Nov 9 | 0 | 0.0 | 582 ms | 0 |
| Nov 10 | 0 | 0.0 | 630 ms | 0 |
| Nov 10 | 0 | 0.0 | 658 ms | 0 |
| Nov 10 | 0 | 0.0 | 657 ms | 0 |
| Nov 10 | 0 | 0.0 | 609 ms | 0 |
| Nov 11 | 0 | 0.0 | 691 ms | 0 |
| Nov 11 | 0 | 0.0 | 553 ms | 0 |
| Nov 11 | 0 | 0.0 | 635 ms | 0 |
| Nov 11 | 0 | 0.0 | 544 ms | 0 |
| Nov 12 | 0 | 0.0 | 568 ms | 0 |
| Nov 12 | 0 | 0.0 | 671 ms | 0 |
| Nov 12 | 0 | 0.0 | 715 ms | 0 |
| Nov 12 | 0 | 0.0 | 668 ms | 0 |
| Nov 13 | 0 | 0.0 | 587 ms | 0 |
| Nov 13 | 0 | 0.0 | 587 ms | 0 |
| Nov 13 | 0 | 0.0 | 668 ms | 0 |
| Nov 13 | 0 | 0.0 | 688 ms | 0 |
| Nov 14 | 0 | 0.0 | 749 ms | 0 |
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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Nabto yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Nabto goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Nabto alerts to Slack, Discord or a webhook — free.
Nabto is listed in our Smart home category and checked at nabto.com. The gatekeeper is your device, not our cloud. Nabto connects apps directly to IoT devices; in the decentralized security models a device admits only the users it is paired with and Nabto routes the connection but can't open one.
Nabto publishes an official status page at status.nabto.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with smart home services: devices showing offline, app control failing, and automations not running.
Measured uptime from our checks: 100% over 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 671 ms average, 553–1046 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Nabto incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
671 ms on average over the last 24 hours (553–1046 ms).
Yes, at https://status.nabto.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For smart home services, watch for devices showing offline, app control failing, and automations not running. If many people report Nabto here at once, the problem is on Nabto'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 Nabto. 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.