AT&T: Service Problems

Life Of This Page

1. 1
   Born
   Oct 29 20:17 UTC
   A second, independent provider or measurement sees it.
2. 2
   Developing
   Oct 29 20:17 UTC
   Reports and measurements join.
3. 3
   Confirmed
   Oct 29 20:17 UTC
   A provider status page acknowledges it.
4. 4
   Resolved · Now
   Oct 30 21:57 UTC
   Every provider marks it resolved and 6 hours pass quietly, or 24 hours pass with no new signal.
5. 5
   Archived
   Not yet
   30 days after resolved. Read only; the link keeps working. Reopens if it comes back.

The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.

Outage Lifecycle

1. First Report: reached
   Oct 29 17:54 UTC
   C123 Provider status pages (Statuspage)
2. Corroborated: reached
   Oct 29 20:17 UTC
   2 independent sources
3. Acknowledged: reached
   Oct 29 17:54 UTC
   C123 status page
4. Network Check: reached
   Oct 29 17:54 UTC
   C111 IODA: network normal (lowest 99.7%)
5. Restored: reached
   Oct 30 21:57 UTC
   All status incidents resolved

Timeline

Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.

AT&T Network During The Incident

Solid blue line: routes announced. Dashed amber line: networks answering pings. Both as a share of AT&T's normal, from C111 IODA, lowest reading in each 2 hours; the shaded band is the incident. The network itself stayed at normal (lowest 99.7%): the problem was in the service, not the network.