Live  /  Networks  /  AT&T

AT&T network health

AS7018 AS20057 AS2386 AS6389 +6 moreNormal

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

Right now

306 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)30599.7%
+25 to +50 ms (elevated)10.3%
+51 to +150 ms (high)00.0%
+151 ms and up (severe)00.0%
Unreachable (no route)0

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

2026-09-05: 3.6%2026-09-06: 3.9%2026-09-07: 4.2%2026-09-08: 4.1%2026-09-09: 3.2%2026-09-10: 4.0%2026-09-11: 3.7%2026-09-12: 3.5%2026-09-13: 3.4%2026-09-14: 3.5%2026-09-15: 3.5%2026-09-16: 4.5%2026-09-17: 3.9%2026-09-18: 3.3%2026-09-19: 3.9%2026-09-20: 4.4%2026-09-21: 4.0%2026-09-22: 4.0%2026-09-23: 3.3%2026-09-24: 3.0%2026-09-25: 3.5%2026-09-26: 3.7%2026-09-27: 3.9%2026-09-28: 3.7%2026-09-29: 3.6%2026-09-30: 3.7%2026-10-01: 5.8%2026-10-02: 3.6%2026-10-03: 4.0%2026-10-04 (so far): 3.6%typical day: 3.7%2026-09-05today
Day (UTC)Paths sampledOver normalShareAverage change
2026-10-031,799724.0%+1.4 ms
2026-10-021,795643.6%+1.4 ms
2026-10-012,4531435.8%+1.7 ms
2026-09-301,836683.7%+1.5 ms
2026-09-291,718623.6%+1.5 ms
2026-09-281,686633.7%+1.5 ms
2026-09-271,685663.9%+1.4 ms

No day in this period stood out from AT&T’s usual background.

Official status

No comprehensive official status feed. AT&T's Business Notification Center requires an account. There is no public status feed. Everything on this page is SquidGrid’s own measurement.

Is it AT&T, or the route to it?

A network-wide figure tells you whether AT&T 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 AT&T 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: AS7018, AS20057, AS2386, AS6389, AS7132, AS7287, AS14654, AS2686, AS2687, AS2688. Updated hourly; times in UTC. SquidGrid is not affiliated with AT&T.