User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
ubivox.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 1 hr ago. Last stored result reached it in 1230 ms.
All clear
All systems operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 13:15 | 0 | 0.0 | 1030 ms | 0 |
| 15:30 | 0 | 0.0 | 1067 ms | 0 |
| 17:30 | 0 | 0.0 | 1133 ms | 0 |
| 19:30 | 0 | 0.0 | 1141 ms | 0 |
| 21:45 | 0 | 0.0 | 1170 ms | 0 |
| 23:45 | 0 | 0.0 | 1178 ms | 0 |
| 01:45 | 0 | 0.0 | 473 ms | 0 |
| 03:45 | 0 | 0.0 | 1178 ms | 0 |
| 06:00 | 0 | 0.0 | 955 ms | 0 |
| 08:00 | 0 | 0.0 | 1282 ms | 0 |
| 10:15 | 0 | 0.0 | 986 ms | 0 |
| 11:00 | 0 | 0.0 | 1230 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 7 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Ubivox 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 Ubivox goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ubivox alerts to Slack, Discord or a webhook — free.
We track Ubivox (ubivox.com) as part of the Cloud & developer group. Municipalities, agencies and ministries send from Ubivox, because the send has to be correct, meet the requirements and stand up to documentation.
Ubivox publishes an official status page at status.ubivox.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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 1023 ms average, 143–1282 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Ubivox incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1023 ms on average over the last 24 hours (143–1282 ms).
Yes, at https://status.ubivox.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 Ubivox here at once, the problem is on Ubivox'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 Ubivox. 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.