User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
frontier.com · Telecom
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests frontier.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 235 ms · 4 min ago.
No status feed
Frontier does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 203 ms | 0 |
| 11:45 | 0 | 0.0 | 206 ms | 0 |
| 12:00 | 0 | 0.0 | 238 ms | 0 |
| 12:15 | 0 | 0.0 | 239 ms | 0 |
| 12:30 | 0 | 0.0 | 86 ms | 0 |
| 12:45 | 0 | 0.0 | 298 ms | 0 |
| 13:00 | 0 | 0.0 | 268 ms | 0 |
| 13:15 | 0 | 0.0 | 156 ms | 0 |
| 13:30 | 0 | 0.0 | 364 ms | 0 |
| 13:45 | 0 | 0.0 | 332 ms | 0 |
| 14:00 | 0 | 0.0 | 177 ms | 0 |
| 14:15 | 0 | 0.0 | 254 ms | 0 |
| 14:30 | 0 | 0.0 | 268 ms | 0 |
| 14:45 | 0 | 0.0 | 276 ms | 0 |
| 15:00 | 0 | 0.0 | 82 ms | 0 |
| 15:15 | 0 | 0.0 | 152 ms | 0 |
| 15:30 | 0 | 0.0 | 225 ms | 0 |
| 15:45 | 0 | 0.0 | 110 ms | 0 |
| 16:00 | 0 | 0.0 | 299 ms | 0 |
| 16:15 | 0 | 0.0 | 310 ms | 0 |
| 16:30 | 0 | 0.0 | 280 ms | 0 |
| 16:45 | 0 | 0.0 | 89 ms | 0 |
| 17:00 | 0 | 0.0 | 165 ms | 0 |
| 17:15 | 0 | 0.0 | 144 ms | 0 |
| 17:30 | 0 | 0.0 | 84 ms | 0 |
| 17:45 | 0 | 0.0 | 376 ms | 0 |
| 18:00 | 0 | 0.0 | 119 ms | 0 |
| 18:15 | 0 | 0.0 | 243 ms | 0 |
| 18:30 | 0 | 0.0 | 235 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 Frontier 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 Frontier 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.