User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 19 min ago. Last stored result reached it in 209 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 243 ms | 0 |
| Tue 00 | 0 | 0.0 | 258 ms | 0 |
| Tue 02 | 0 | 0.0 | 201 ms | 0 |
| Tue 04 | 0 | 0.0 | 183 ms | 0 |
| Tue 06 | 0 | 0.0 | 149 ms | 0 |
| Tue 08 | 0 | 0.0 | 204 ms | 0 |
| Tue 10 | 0 | 0.0 | 204 ms | 0 |
| Tue 12 | 0 | 0.0 | 77 ms | 0 |
| Tue 15 | 0 | 0.0 | 242 ms | 0 |
| Tue 17 | 0 | 0.0 | 266 ms | 0 |
| Tue 19 | 0 | 0.0 | 93 ms | 0 |
| Tue 21 | 0 | 0.0 | 235 ms | 0 |
| Wed 00 | 0 | 0.0 | 309 ms | 0 |
| Wed 02 | 0 | 0.0 | 173 ms | 0 |
| Wed 04 | 0 | 0.0 | 202 ms | 0 |
| Wed 06 | 0 | 0.0 | 204 ms | 0 |
| Wed 07 | 0 | 0.0 | 271 ms | 0 |
| Wed 09 | 0 | 0.0 | 80 ms | 0 |
| Wed 11 | 0 | 0.0 | 122 ms | 0 |
| Wed 13 | 0 | 0.0 | 252 ms | 0 |
| Wed 15 | 0 | 0.0 | 81 ms | 0 |
| Wed 18 | 0 | 0.0 | 249 ms | 0 |
| Wed 20 | 0 | 0.0 | 250 ms | 0 |
| Wed 22 | 0 | 0.0 | 286 ms | 0 |
| Thu 00 | 0 | 0.0 | 193 ms | 0 |
| Thu 02 | 0 | 0.0 | 101 ms | 0 |
| Thu 04 | 0 | 0.0 | 164 ms | 0 |
| Thu 07 | 0 | 0.0 | 207 ms | 0 |
| Thu 09 | 0 | 0.0 | 87 ms | 0 |
| Thu 11 | 0 | 0.0 | 124 ms | 0 |
| Thu 13 | 0 | 0.0 | 73 ms | 0 |
| Thu 15 | 0 | 0.0 | 256 ms | 0 |
| Thu 17 | 0 | 0.0 | 101 ms | 0 |
| Thu 19 | 0 | 0.0 | 173 ms | 0 |
| Thu 21 | 0 | 0.0 | 114 ms | 0 |
| Thu 23 | 0 | 0.0 | 182 ms | 0 |
| Fri 00 | 0 | 0.0 | 193 ms | 0 |
| Fri 02 | 0 | 0.0 | 57 ms | 0 |
| Fri 04 | 0 | 0.0 | 320 ms | 0 |
| Fri 06 | 0 | 0.0 | 228 ms | 0 |
| Fri 08 | 0 | 0.0 | 181 ms | 0 |
| Fri 10 | 0 | 0.0 | 210 ms | 0 |
| Fri 11 | 0 | 0.0 | 179 ms | 0 |
| Fri 13 | 0 | 0.0 | 81 ms | 0 |
| Fri 15 | 0 | 0.0 | 215 ms | 0 |
| Fri 17 | 0 | 0.0 | 237 ms | 0 |
| Fri 18 | 0 | 0.0 | 198 ms | 0 |
| Fri 20 | 0 | 0.0 | 209 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 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Viam 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 Viam goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Viam alerts to Slack, Discord or a webhook — free.
Viam, at viam.com, is one of the Cloud & developer services we monitor. Agentic infrastructure to develop, deploy, and operate robotics applications safely.
Viam publishes an official status page at status.viam.com; 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: 188 ms average, 57–320 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Viam incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
188 ms on average over the last 24 hours (57–320 ms).
Yes, at https://status.viam.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 Viam here at once, the problem is on Viam'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 Viam. 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.