Multi-State AT&T U-Verse Outage Enters Third Day

SonicSpike writes "AT&T U-verse customers are reporting this morning that an outage that began Monday and is affecting at least 15 states is still not resolved. Some customers were told this morning that the problem will not be fixed for at least 24 hours."

Comments

This is surprising

[Anonymous Coward]

After all, AT&T charges some of the highest rates for internet access in the world, and it's very slow. I assumed that this was because all the money was going into rock solid reliability instead of speed. Right? Right?

Re:This is surprising

[Andy Dodd]

Obviously the CEO is using reliability via redundancy. If he has 10 fast Italian cars, he's got a decent chance that at least one works at any given time.

Re:Which states?

[Anonymous Coward]

Arkansas, Georgia, Texas, Louisiana, South Carolina, North Carolina, Tennessee, Mississippi, Florida, Kentucky, Alabama and Oklahoma are cited across multiple sources, including http://www.arkansasbusiness.com/article/90315/att-u-verse-experiencing-widespread-outages . I couldn't find any other sources that mentioned three more states, but eyeballing a map of the US, and how some mentioned the 'southwest' too, I suspect Arizona and New Mexico may be involved as well.

Re:Which states?

[Huggs]

http://www.arkansasbusiness.com/article/90315/att-u-verse-experiencing-widespread-outages
Not a complete list, but its limited to more southern states. FTA:

"Arkansas, Georgia, Texas, Louisiana, South Carolina, North Carolina, Tennessee, Mississippi, Florida, Kentucky, Alabama and Oklahoma."

INFORMATION

[Anonymous Coward]

--- anonymous uverse tech
This is whats going on, any new gateway or exisiting gateway that is restarted will not be able to obtain service. The DHCP servers are overloaded and over capacity, CMS has disabled their northbound API so no provisioning can get thru in order to lessen the load.
Its not affecting everyone in the affected areas, and as a precaution NO ONE should attempt to powercycle or reset their gateway for any reason.

Re:It worked better with relays

[Waffle Iron]

You've got some real rose-colored glasses there. I remember what else came along with that monopoly reliability:

-Phones, which you had to rent for decades, wired directly to the wall with no connectors. (That made painting a room into a constant phone shuffle.)
-Rules against hooking anything but rented telco equipment to the system.
-Astronomical per-minute costs to dial up grandma in the next state.
-Switches that were frequently overloaded by too much traffic (fast busy signal). Not technically "down", but frequently unuseable anyway.
-Zero calling features.

If the AT&T monopoly were still in place, we'd probably never have gotten internet access at all. Instead, we'd be probably all be stuck using clunky telco-owned terminals like the French Minitel system.

Re:Which states?

[Anonymous Coward]

Here's all the areas being affected, posting anon since I work for them, and I'm not entirely sure I'm allowed to post this info.

Atlanta (Tucker), GA
Baton Rouge, LA
Birmingham, AL
Charleston, SC
Charlotte, NC
Columbia, SC
Fayetteville, AR
Greensboro, NC
Greenville, SC
Jackson, MS
Jacksonville, FL
Knoxville, TN
Little Rock, AR
Louisville, KY
Memphis, TN
Miami, FL
Mobile, AL
Nashville, TN
New Orleans, LA
Oklahoma City, OK
Orlando (Daytona Beach), FL
Raleigh, NC
Tulsa, OK
West Palm Beach, FL

These areas should be resolved by now:
Austin, TX
Corpus Christi, TX
Dallas (Richardson), TX
El Paso, TX
Houston, TX
Lubbock, TX
Odessa (Midland), TX
San Antonio, TX

Here's what I know about it as a lowly peon in the company: The DHCP daemon on a server in Richardson, TX, can't handle all the DHCP requests, and so keeps restarting every 10 minutes. When it's up, requests go through fine.