Live  /  Networks  /  Verizon

Verizon network health

AS701 AS702 AS6167 AS22394 +2 moreNormal

SquidGrid measures 6,873 internet paths that cross Verizon’s network, from vantage points in 31 countries, and compares each path with its own normal latency. Snapshot 2026-10-04 17:34 UTC.

Right now

279 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 normalPathsShare
Under +25 ms (normal)279100.0%
+25 to +50 ms (elevated)00.0%
+51 to +150 ms (high)00.0%
+151 ms and up (severe)00.0%
Unreachable (no route)0

Routing: 0 of Verizon’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 Verizon paths we sampled that spent at least one hour 25 ms or more over their normal. A typical day is 4.1% (dashed line); a bar turns orange at twice that.

2026-09-05: 4.3%2026-09-06: 4.6%2026-09-07: 4.4%2026-09-08: 4.5%2026-09-09: 4.8%2026-09-10: 4.1%2026-09-11: 4.2%2026-09-12: 3.8%2026-09-13: 4.5%2026-09-14: 4.6%2026-09-15: 4.0%2026-09-16: 4.0%2026-09-17: 4.0%2026-09-18: 3.8%2026-09-19: 4.2%2026-09-20: 4.3%2026-09-21: 4.8%2026-09-22: 4.6%2026-09-23: 4.0%2026-09-24: 4.0%2026-09-25: 4.0%2026-09-26: 3.5%2026-09-27: 4.0%2026-09-28: 4.1%2026-09-29: 4.0%2026-09-30: 3.8%2026-10-01: 6.5%2026-10-02: 4.0%2026-10-03: 3.9%2026-10-04 (so far): 4.5%typical day: 4.1%2026-09-05today
Day (UTC)Paths sampledOver normalShareAverage change
2026-10-031,372543.9%+2.1 ms
2026-10-021,347544.0%+2.1 ms
2026-10-012,2771496.5%+2.3 ms
2026-09-301,412543.8%+2.1 ms
2026-09-291,260504.0%+2.0 ms
2026-09-281,297534.1%+2.0 ms
2026-09-271,390554.0%+2.0 ms

No day in this period stood out from Verizon’s usual background.

Official status

No comprehensive official status feed. Verizon publishes network status only inside its authenticated Enterprise Center. There is no public status feed. Everything on this page is SquidGrid’s own measurement.

Is it Verizon, or the route to it?

A network-wide figure tells you whether Verizon as a whole is having a bad hour. It cannot tell you whether your traffic is affected, or where on the route it changes.

🔒 Customers
Which handoffs into and out of Verizon 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 →

How to read this: a path’s normal is its own trended median latency, not a speed-of-light estimate. The bands follow SquidGrid’s state scale (+25 / +50 / +150 ms). The header reads Normal while under 2% of currently read paths are 25 ms or more over normal, Elevated from 2%, and Degraded from 10%. ASNs counted: AS701, AS702, AS6167, AS22394, AS7046, AS3371. Updated hourly; times in UTC. SquidGrid is not affiliated with Verizon.