User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
ziplyfiber.com · Telecom
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests ziplyfiber.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.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 13 ms · 1 min ago.
No status feed
Ziply Fiber does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 01:15 | 0 | 0.0 | 82 ms | 0 |
| 01:30 | 0 | 0.0 | 101 ms | 0 |
| 01:45 | 0 | 0.0 | 139 ms | 0 |
| 02:00 | 0 | 0.0 | 204 ms | 0 |
| 02:15 | 0 | 0.0 | 73 ms | 0 |
| 02:30 | 0 | 0.0 | 198 ms | 0 |
| 02:45 | 0 | 0.0 | 201 ms | 0 |
| 03:00 | 0 | 0.0 | 136 ms | 0 |
| 03:15 | 0 | 0.0 | 216 ms | 0 |
| 03:30 | 0 | 0.0 | 70 ms | 0 |
| 03:45 | 0 | 0.0 | 102 ms | 0 |
| 04:00 | 0 | 0.0 | 146 ms | 0 |
| 04:15 | 0 | 0.0 | 284 ms | 0 |
| 04:30 | 0 | 0.0 | 19 ms | 0 |
| 04:45 | 0 | 0.0 | 59 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.
No outages on record for Ziply Fiber 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 Ziply Fiber goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Ziply Fiber alerts to Slack, Discord or a webhook — free.
Checks are succeeding and user reports are near the baseline.
If Ziply Fiber is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Ziply Fiber's side.
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.