User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Telecom
optimum.net · Telecom
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Tests optimum.net 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 439 ms · 2 min ago.
No status feed
Optimum does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 11:30 | 0 | 0.0 | 915 ms | 0 |
| 11:45 | 0 | 0.0 | 232 ms | 0 |
| 12:00 | 0 | 0.0 | 539 ms | 0 |
| 12:15 | 0 | 0.0 | 652 ms | 0 |
| 12:30 | 0 | 0.0 | 254 ms | 0 |
| 12:45 | 0 | 0.0 | 548 ms | 0 |
| 13:00 | 0 | 0.0 | 417 ms | 0 |
| 13:15 | 0 | 0.0 | 1118 ms | 0 |
| 13:30 | 0 | 0.0 | 529 ms | 0 |
| 13:45 | 0 | 0.0 | 488 ms | 0 |
| 14:00 | 0 | 0.0 | 433 ms | 0 |
| 14:15 | 0 | 0.0 | 490 ms | 0 |
| 14:30 | 0 | 0.0 | 811 ms | 0 |
| 14:45 | 0 | 0.0 | 288 ms | 0 |
| 15:00 | 0 | 0.0 | 310 ms | 0 |
| 15:15 | 0 | 0.0 | 262 ms | 0 |
| 15:30 | 0 | 0.0 | 441 ms | 0 |
| 15:45 | 0 | 0.0 | 459 ms | 0 |
| 16:00 | 0 | 0.0 | 363 ms | 0 |
| 16:15 | 0 | 0.0 | 473 ms | 0 |
| 16:30 | 0 | 0.0 | 889 ms | 0 |
| 16:45 | 0 | 0.0 | 200 ms | 0 |
| 17:00 | 0 | 0.0 | 439 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 Optimum 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 Optimum 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.