User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
visible.com · Telecom
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests visible.com from your browser and compares it with our checks, the official status, and user reports.
Press Run testNothing leaves your browser except a request to the site and to us.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 171 ms · 2 min ago.
No status feed
Visible does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 245 ms | 0 |
| 11:45 | 0 | 0.0 | 239 ms | 0 |
| 12:00 | 0 | 0.0 | 171 ms | 0 |
| 12:15 | 0 | 0.0 | 193 ms | 0 |
| 12:30 | 0 | 0.0 | 212 ms | 0 |
| 12:45 | 0 | 0.0 | 253 ms | 0 |
| 13:00 | 0 | 0.0 | 148 ms | 0 |
| 13:15 | 0 | 0.0 | 378 ms | 0 |
| 13:30 | 0 | 0.0 | 260 ms | 0 |
| 13:45 | 0 | 0.0 | 294 ms | 0 |
| 14:00 | 0 | 0.0 | 173 ms | 0 |
| 14:15 | 0 | 0.0 | 256 ms | 0 |
| 14:30 | 0 | 0.0 | 173 ms | 0 |
| 14:45 | 0 | 0.0 | 169 ms | 0 |
| 15:00 | 0 | 0.0 | 196 ms | 0 |
| 15:15 | 0 | 0.0 | 171 ms | 0 |
| 15:30 | 0 | 0.0 | 194 ms | 0 |
| 15:45 | 0 | 0.0 | 108 ms | 0 |
| 16:00 | 0 | 0.0 | 167 ms | 0 |
| 16:15 | 0 | 0.0 | 286 ms | 0 |
| 16:30 | 0 | 0.0 | 221 ms | 0 |
| 16:45 | 0 | 0.0 | 210 ms | 0 |
| 17:00 | 0 | 0.0 | 142 ms | 0 |
| 17:15 | 0 | 0.0 | 243 ms | 0 |
| 17:30 | 0 | 0.0 | 106 ms | 0 |
| 17:45 | 0 | 0.0 | 183 ms | 0 |
| 18:00 | 0 | 0.0 | 222 ms | 0 |
| 18:15 | 0 | 0.0 | 179 ms | 0 |
| 18:30 | 0 | 0.0 | 153 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed this status badge · JSON
No outages on record for Visible 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 Visible goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Checks are succeeding and user reports are near the baseline.
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.