Live / Networks / Cox
Cox network health
AS22773Normal
SquidGrid measures 904 internet paths that cross Cox’s network, from vantage points in 8 countries, and compares each path with its own normal latency. Snapshot 2026-10-04 17:34 UTC.
Right now
36 of these paths have a reading from the last six hours. The typical path is running +0.0 ms against its own normal.
| Change vs each path’s normal | Paths | Share |
|---|
| Under +25 ms (normal) | 36 | 100.0% |
| +25 to +50 ms (elevated) | 0 | 0.0% |
| +51 to +150 ms (high) | 0 | 0.0% |
| +151 ms and up (severe) | 0 | 0.0% |
| Unreachable (no route) | 0 | |
Routing: 0 of Cox’s measured paths sit inside a prefix that was withdrawn from BGP or changed route in the last two hours.
The last 30 days
Each bar is one UTC day: the share of Cox paths we sampled that spent at least one hour 25 ms or more over their normal. A typical day is 0.5% (dashed line); a bar turns orange at twice that.
| Day (UTC) | Paths sampled | Over normal | Share | Average change |
|---|
| 2026-10-03 | 227 | 1 | 0.4% | +3.1 ms |
| 2026-10-02 | 210 | 1 | 0.5% | +3.2 ms |
| 2026-10-01 | 390 | 8 | 2.1% | +3.5 ms |
| 2026-09-30 | 237 | 1 | 0.4% | +3.1 ms |
| 2026-09-29 | 236 | 1 | 0.4% | +3.0 ms |
| 2026-09-28 | 226 | 1 | 0.4% | +3.0 ms |
| 2026-09-27 | 220 | 1 | 0.5% | +3.0 ms |
No day in this period stood out from Cox’s usual background.
Official status
No comprehensive official status feed. No public, network-wide status feed from Cox is on record. Everything on this page is SquidGrid’s own measurement.
Is it Cox, or the route to it?
A network-wide figure tells you whether Cox as a whole is having a bad hour. It cannot tell you whether your traffic is affected, or where on the route it changes.
🔒 CustomersWhich handoffs into and out of Cox are off baseline, and in which cities
The carrier on each side of the stretch where conditions change
Alerts when your own sites’ paths cross a degraded stretch
Included with any paid plan.
See plans →