Reports are filtering in from hither and yon that AT&T's Uverse (or U-Verse, as it's sometimes spelled) service is having problems in multiple markets on 29 October 2013. It's not clear yet the extent of the problem, how widespread the outages are, and what the root cause of the issue is.
This problem is also noted by DownDetector, a fabulous resource for figuring out who to point a finger at when things go wrong. The DownDetector ATT status at 2:30p EST on 29 October 2013 notes recent troubles in Chicago, Los Angeles, Dallas, Oakland, Richmond, Napa, Atlanta, Jefferson City, Tracy, and Indianapolis.
This Reddit thread purports to have a root cause, though nothing official has been released yet as of 10:00pm EST. From Redditor Jx22:
all ipdslams received an update last night, causing all rg's (residential gateways) to have to reauth and the authentication servers cant cope, basically a ddos.
The Chicago Tribune reports
AT&T is working to fix a U-Verse service outage in the Chicago area after a “software upgrade issue,” the company said Tuesday.
“A limited number of U-verse customers may be experiencing issues with U-verse services due to a software upgrade issue,” AT&T said in a statement. “Technicians have resolved the issue, and service has been restored for most impacted customers. We expect service to be fully restored for all customers by early afternoon. We apologize for this inconvenience.”
Los Angeles, California
Uverse is still down in LA. Coming up on 12 hours now. And I probably still won't get the speed I pay for.— Nic Birdsall (@nbirdsall) October 29, 2013
@Uverse Internet in 78701 has been down since 6 am, can't get anyone on phone. Please advise.— Sarah Saxon (@SarahASaxon) October 29, 2013
More details as they appear.