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 48 min ago. Last stored result reached it in 432 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 18 | 0 | 0.0 | 492 ms | 0 |
| Mon 20 | 0 | 0.0 | 418 ms | 0 |
| Mon 22 | 0 | 0.0 | 503 ms | 0 |
| Tue 00 | 0 | 0.0 | 416 ms | 0 |
| Tue 02 | 0 | 0.0 | 487 ms | 0 |
| Tue 04 | 0 | 0.0 | 452 ms | 0 |
| Tue 06 | 0 | 0.0 | 426 ms | 0 |
| Tue 09 | 0 | 0.0 | 928 ms | 0 |
| Tue 11 | 0 | 0.0 | 603 ms | 0 |
| Tue 13 | 0 | 0.0 | 899 ms | 0 |
| Tue 15 | 0 | 0.0 | 441 ms | 0 |
| Tue 17 | 0 | 0.0 | 919 ms | 0 |
| Tue 20 | 0 | 0.0 | 415 ms | 0 |
| Tue 22 | 0 | 0.0 | 511 ms | 0 |
| Wed 00 | 0 | 0.0 | 897 ms | 0 |
| Wed 02 | 0 | 0.0 | 498 ms | 0 |
| Wed 05 | 0 | 0.0 | 419 ms | 0 |
| Wed 07 | 0 | 0.0 | 901 ms | 0 |
| Wed 09 | 0 | 0.0 | 464 ms | 0 |
| Wed 11 | 0 | 0.0 | 448 ms | 0 |
| Wed 14 | 0 | 0.0 | 373 ms | 0 |
| Wed 16 | 0 | 0.0 | 461 ms | 0 |
| Wed 18 | 0 | 0.0 | 779 ms | 0 |
| Wed 20 | 0 | 0.0 | 410 ms | 0 |
| Wed 22 | 0 | 0.0 | 432 ms | 0 |
| Thu 00 | 0 | 0.0 | 962 ms | 0 |
| Thu 03 | 0 | 0.0 | 473 ms | 0 |
| Thu 05 | 0 | 0.0 | 450 ms | 0 |
| Thu 07 | 0 | 0.0 | 901 ms | 0 |
| Thu 09 | 0 | 0.0 | 438 ms | 0 |
| Thu 11 | 0 | 0.0 | 973 ms | 0 |
| Thu 13 | 0 | 0.0 | 485 ms | 0 |
| Thu 15 | 0 | 0.0 | 752 ms | 0 |
| Thu 17 | 0 | 0.0 | 319 ms | 0 |
| Thu 19 | 0 | 0.0 | 521 ms | 0 |
| Thu 21 | 0 | 0.0 | 445 ms | 0 |
| Thu 23 | 0 | 0.0 | 497 ms | 0 |
| Fri 01 | 0 | 0.0 | 436 ms | 0 |
| Fri 03 | 0 | 0.0 | 398 ms | 0 |
| Fri 05 | 0 | 0.0 | 360 ms | 0 |
| Fri 07 | 0 | 0.0 | 478 ms | 0 |
| Fri 09 | 0 | 0.0 | 411 ms | 0 |
| Fri 10 | 0 | 0.0 | 429 ms | 0 |
| Fri 12 | 0 | 0.0 | 904 ms | 0 |
| Fri 14 | 0 | 0.0 | 441 ms | 0 |
| Fri 16 | 0 | 0.0 | 474 ms | 0 |
| Fri 18 | 0 | 0.0 | 669 ms | 0 |
| Fri 19 | 0 | 0.0 | 432 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 Priva 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 Priva goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Priva alerts to Slack, Discord or a webhook — free.
We track Priva (priva.com) as part of the Cloud & developer group. Priva is a high-tech company in the climate control field, specializing in smart building automation, greenhouse technology & indoor farming. Discover more!
Priva publishes an official status page at status.priva.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 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 492 ms average, 243–904 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 Priva incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
492 ms on average over the last 24 hours (243–904 ms).
Yes, at https://status.priva.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 Priva here at once, the problem is on Priva'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 Priva. 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.