User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
navvis.com · Cloud & developer
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 35 min ago. Last stored result reached it in 78 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Thu 05 | 0 | 0.0 | 38 ms | 0 |
| Thu 07 | 0 | 0.0 | 53 ms | 0 |
| Thu 09 | 0 | 0.0 | 110 ms | 0 |
| Thu 11 | 0 | 0.0 | 15 ms | 0 |
| Thu 13 | 0 | 0.0 | 58 ms | 0 |
| Thu 15 | 0 | 0.0 | 81 ms | 0 |
| Thu 17 | 0 | 0.0 | 74 ms | 0 |
| Thu 19 | 0 | 0.0 | 42 ms | 0 |
| Thu 21 | 0 | 0.0 | 48 ms | 0 |
| Thu 23 | 0 | 0.0 | 74 ms | 0 |
| Fri 02 | 0 | 0.0 | 46 ms | 0 |
| Fri 04 | 0 | 0.0 | 20 ms | 0 |
| Fri 06 | 0 | 0.0 | 26 ms | 0 |
| Fri 08 | 0 | 0.0 | 25 ms | 0 |
| Fri 10 | 0 | 0.0 | 22 ms | 0 |
| Fri 11 | 0 | 0.0 | 35 ms | 0 |
| Fri 12 | 0 | 0.0 | 80 ms | 0 |
| Fri 14 | 0 | 0.0 | 99 ms | 0 |
| Fri 16 | 0 | 0.0 | 77 ms | 0 |
| Fri 18 | 0 | 0.0 | 69 ms | 0 |
| Fri 20 | 0 | 0.0 | 47 ms | 0 |
| Fri 22 | 0 | 0.0 | 20 ms | 0 |
| Sat 00 | 0 | 0.0 | 76 ms | 0 |
| Sat 02 | 0 | 0.0 | 24 ms | 0 |
| Sat 04 | 0 | 0.0 | 51 ms | 0 |
| Sat 06 | 0 | 0.0 | 31 ms | 0 |
| Sat 08 | 0 | 0.0 | 21 ms | 0 |
| Sat 11 | 0 | 0.0 | 17 ms | 0 |
| Sat 14 | 0 | 0.0 | 18 ms | 0 |
| Sat 16 | 0 | 0.0 | 56 ms | 0 |
| Sat 19 | 0 | 0.0 | 30 ms | 0 |
| Sat 21 | 0 | 0.0 | 49 ms | 0 |
| Sat 23 | 0 | 0.0 | 37 ms | 0 |
| Sun 02 | 0 | 0.0 | 59 ms | 0 |
| Sun 03 | 0 | 0.0 | 29 ms | 0 |
| Sun 05 | 0 | 0.0 | 45 ms | 0 |
| Sun 07 | 0 | 0.0 | 22 ms | 0 |
| Sun 10 | 0 | 0.0 | 19 ms | 0 |
| Sun 11 | 0 | 0.0 | 15 ms | 0 |
| Sun 13 | 0 | 0.0 | 15 ms | 0 |
| Sun 15 | 0 | 0.0 | 57 ms | 0 |
| Sun 17 | 0 | 0.0 | 43 ms | 0 |
| Sun 19 | 0 | 0.0 | 22 ms | 0 |
| Sun 20 | 0 | 0.0 | 73 ms | 0 |
| Sun 21 | 0 | 0.0 | 36 ms | 0 |
| Sun 23 | 0 | 0.0 | 165 ms | 0 |
| Mon 01 | 0 | 0.0 | 37 ms | 0 |
| Mon 03 | 0 | 0.0 | 78 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 11 days of data so far, so the 90-day numbers fill in over time.
No outages on record for NavVis 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 NavVis goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send confirmed down and recovery alerts to Slack, Discord or a webhook — free. Early warnings are part of Owner Alerts.
We track NavVis (navvis.com) as part of the Cloud & developer group. NavVis's ground-breaking reality capture technology allows accurate scanning of complex sites at scale and digital twin solutions for various industries.
NavVis publishes an official status page at status.navvis.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 11 days of checks. No public incidents logged since monitoring began 11 days ago.
Response time over the last 24 hours: 55 ms average, 15–250 ms range across 17 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public NavVis incident since monitoring began 11 days ago.
From our own checks: 100% over 11 days of checks.
55 ms on average over the last 24 hours (15–250 ms).
Yes, at https://status.navvis.com.
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 NavVis here at once, the problem is on NavVis'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 NavVis. 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.