AT&T outage, 2 November 2026
AT&T was down for 21 minutes on 2 November 2026, from 17:06 to 17:27 UTC, as measured by HostTracker's checkpoints.
Resolved
Outage measured by HostTracker's checkpoints
- Started
- 17:06
- 2 Nov 2026 UTC
- Ended
- 17:27
- 2 Nov 2026 UTC
- Duration
- 21m
- 21 minutes
- Checkpoints
- 1
- reported a failure
- Most common error
- Http 403
- as reported by our checks
What our checkpoints saw
All times UTC.
The first failed check is the top row, and the recovery is the last one. A row marked "x N" stands for several consecutive checks with the same result from that checkpoint.
| Time (UTC) | Location | Result | Error |
|---|---|---|---|
| 2 Nov 17:16 | Moscow, Russian Federation | Failedx 2 | Http 403 |
Response time around the outage
474ms low · 40002ms peak
2 Nov 15:41 to 2 Nov 17:16 UTC
The shaded band is the outage window. Points are averaged per bucket across the checkpoints that answered, so a gap in the line is a period where nothing answered at all.
Previous outage
2 Nov 2026 15:32 UTCNext outage
This is the most recent outage we recorded.
Does your product depend on AT&T?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with AT&T.