User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
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 49 min ago. Last stored result reached it in 168 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 23 | 0 | 0.0 | 143 ms | 0 |
| Tue 01 | 0 | 0.0 | 131 ms | 0 |
| Tue 03 | 0 | 0.0 | 82 ms | 0 |
| Tue 05 | 0 | 0.0 | 198 ms | 0 |
| Tue 08 | 0 | 0.0 | 131 ms | 0 |
| Tue 10 | 0 | 0.0 | 188 ms | 0 |
| Tue 12 | 0 | 0.0 | 302 ms | 0 |
| Tue 14 | 0 | 0.0 | 964 ms | 0 |
| Tue 16 | 0 | 0.0 | 211 ms | 0 |
| Tue 19 | 0 | 0.0 | 695 ms | 0 |
| Tue 21 | 0 | 0.0 | 197 ms | 0 |
| Tue 23 | 0 | 0.0 | 184 ms | 0 |
| Wed 01 | 0 | 0.0 | 234 ms | 0 |
| Wed 04 | 0 | 0.0 | 322 ms | 0 |
| Wed 06 | 0 | 0.0 | 280 ms | 0 |
| Wed 08 | 0 | 0.0 | 186 ms | 0 |
| Wed 10 | 0 | 0.0 | 365 ms | 0 |
| Wed 13 | 0 | 0.0 | 143 ms | 0 |
| Wed 15 | 0 | 0.0 | 203 ms | 0 |
| Wed 17 | 0 | 0.0 | 189 ms | 0 |
| Wed 19 | 0 | 0.0 | 192 ms | 0 |
| Wed 21 | 0 | 0.0 | 181 ms | 0 |
| Wed 23 | 0 | 0.0 | 206 ms | 0 |
| Thu 02 | 0 | 0.0 | 383 ms | 0 |
| Thu 04 | 0 | 0.0 | 248 ms | 0 |
| Thu 06 | 0 | 0.0 | 154 ms | 0 |
| Thu 08 | 0 | 0.0 | 132 ms | 0 |
| Thu 10 | 0 | 0.0 | 344 ms | 0 |
| Thu 12 | 0 | 0.0 | 144 ms | 0 |
| Thu 14 | 0 | 0.0 | 57 ms | 0 |
| Thu 16 | 0 | 0.0 | 224 ms | 0 |
| Thu 18 | 0 | 0.0 | 366 ms | 0 |
| Thu 20 | 0 | 0.0 | 202 ms | 0 |
| Thu 21 | 0 | 0.0 | 1283 ms | 0 |
| Thu 23 | 0 | 0.0 | 341 ms | 0 |
| Fri 00 | 0 | 0.0 | 134 ms | 0 |
| Fri 02 | 0 | 0.0 | 114 ms | 0 |
| Fri 04 | 0 | 0.0 | 46 ms | 0 |
| Fri 06 | 0 | 0.0 | 214 ms | 0 |
| Fri 08 | 0 | 0.0 | 46 ms | 0 |
| Fri 10 | 0 | 0.0 | 161 ms | 0 |
| Fri 11 | 0 | 0.0 | 198 ms | 0 |
| Fri 13 | 0 | 0.0 | 134 ms | 0 |
| Fri 15 | 0 | 0.0 | 59 ms | 0 |
| Fri 17 | 0 | 0.0 | 50 ms | 0 |
| Fri 19 | 0 | 0.0 | 67 ms | 0 |
| Fri 20 | 0 | 0.0 | 150 ms | 0 |
| Fri 21 | 0 | 0.0 | 168 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 Vero 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 Vero goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Vero alerts to Slack, Discord or a webhook — free.
We track Vero (getvero.com) as part of the Telecom group. Send personalized emails, mobile push notifications and SMS messages to your users based on what they do in your product.
Vero publishes an official status page at status.getvero.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with telecom services: no service or data, account and billing pages failing, and app sign-in problems.
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: 134 ms average, 46–341 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 Vero incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
134 ms on average over the last 24 hours (46–341 ms).
Yes, at https://status.getvero.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For telecom services, watch for no service or data, account and billing pages failing, and app sign-in problems. If many people report Vero here at once, the problem is on Vero'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 Vero. 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.