Skip to main content
OUTAGE RESOLVED · UTC

AT&T outage, 2 October 2026

AT&T was down for 1 hour 12 minutes on 2 October 2026, from 13:51 to 15:03 UTC, as measured by HostTracker's checkpoints.

STARTED
13:51
2 Oct 2026 UTC
ENDED
15:03
2 Oct 2026 UTC
DURATION
71.9m
1 hour 12 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.

Individual checks recorded during the AT&T outage on 2 October 2026, all times UTC
Time (UTC) Location Result Error
2 Oct 14:02 Krasnodar2, Russian Federation Failed x 6 Http 403
2 Oct 15:03 Krasnodar2, Russian Federation Failed Http 403
Response time around the outage
809ms low · 1994ms peak
2 Oct 12:49 to 2 Oct 15:02 UTC
1994 ms 809 ms 2 Oct 12:49 UTC 2 Oct 15:02 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.

Your own monitoring

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.