AT&T is a disaster today

#0 - Sept. 23, 2010, 7:06 p.m.

6 173 ms 173 ms 177 ms cr2.la2ca.ip.att.net [12.122.129.62]
7 174 ms 174 ms 174 ms cr1.slkut.ip.att.net [12.122.30.29]
8 * 174 ms 175 ms cr2.dvmco.ip.att.net [12.122.30.26]
9 173 ms 174 ms 173 ms cr1.cgcil.ip.att.net [12.122.31.86]
10 176 ms 173 ms 172 ms cr83.cgcil.ip.att.net [12.123.7.109]
11 * 175 ms 174 ms gar29.cgcil.ip.att.net [12.123.7.9]
12 174 ms * 173 ms 12-122-254-174.attens.net [12.122.254.174]
13 175 ms 173 ms 173 ms 63.240.130.206

Is anybody working on this? Playing with 2000ms responses is not very fun. Dallas data center.

Harlsoco

#15 - Sept. 23, 2010, 7:39 p.m.

This is indeed a tech issue, Tendra, but it appears as though you may not be alone. I was able to find this sticky on the Technical Support Forum:

DC'ing in 10 seconds? Texas?
http://forums.worldofwarcraft.com/thread.html?topicId=26850267990&sid=1

I encourage you and anyone else experiencing this issue to post in that thread with the necessary information.