Ok so this is the second night in a row this has been going on. Although earlier today I was able to play fine with no latency problems from 12pm to 3pm EST. Last night and tonight as soon as it gets near 8pm EST though I'm getting an avg 400-600 latency. I've contacted my ISP (Time Warner Cable) and had them check the tracert as well they say that there isn't anything they can really do though since it is outside their network. I'm located in NC if that helps at all. I've included a copy of my tracert results below and as you can see it clearly shows the issues being on AT&T's network. Since I'm not a customer of AT&T I can't call them and make them aware of the issue and request a resolution but blizzard is their customer so could someone please do us (your paying customers) a favor and escalate the issue to them as this is just unacceptable game play in it's current state.
Tracing route to 206.16.23.77 over a maximum of 30 hops
1 9 ms 10 ms 7 ms 10.100.160.1
2 12 ms 9 ms 12 ms gig2-1-0.gnboncsg-rtr2.triad.rr.com [24.28.228.238]
3 12 ms 14 ms 13 ms ge-3-1-0.chrlncpop-rtr1.southeast.rr.com [24.93.64.162]
4 12 ms 14 ms 13 ms te-3-3.car1.Charlotte1.Level3.net [4.71.124.1]
5 21 ms 17 ms 18 ms ae-4-4.ebr1.Atlanta2.Level3.net [4.69.132.162]
6 17 ms 17 ms 20 ms ae-18-51.car2.Atlanta4.Level3.net [4.68.103.13]
7 101 ms 102 ms 105 ms 192.205.35.213
8 119 ms 125 ms * cr1.attga.ip.att.net [12.122.82.98]
9 127 ms 124 ms 124 ms cr2.dlstx.ip.att.net [12.122.28.174]
10 127 ms 126 ms 139 ms gar5.dlstx.ip.att.net [12.122.138.5]
11 125 ms 128 ms 132 ms mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
12 * 149 ms 129 ms mdf002fbi8ks0002-eth-2-1.dal1.attens.net [63.241.192.114]
I'm aware just want to try to keep things clean in the thread. It's hard to get a blue responce as it is without multiple pages of ppl complaining about everything under the sun.
Q u o t e: I'm aware just want to try to keep things clean in the thread. It's hard to get a blue responce as it is without multiple pages of ppl complaining about everything under the sun.
I'm noticing the exact same problems. Past few days have been 400-500 lat, and tonight I had to pass out of a Naxx raid because I would DC 4 shots into a 4H attempt.
Yea like Raq pointed out in another thread it's probably the same issue that happen last year with time warner customers on the east coast and the year before that as well. Sad part is it took FOREVER for blizz to finally work it out with AT&T and TWC. Good thing this is a free service... O wait........
Q u o t e: Yea like Raq pointed out in another thread it's probably the same issue that happen last year with time warner customers on the east coast and the year before that as well. Sad part is it took FOREVER for blizz to finally work it out with AT&T and TWC. Good thing this is a free service... O wait........
I remember that, sucked a lot. :\
Would basically be 1000+ lat after certain times, and it lasted almost a month. Hope like hell they fix this problem faster this time around.
Same here had to stop raiding throughout Sunwell because of it and didn't come back until WOTLK. So pointless that they try to fix stuff when the obviously can't. Should just ship their problems overseas like the rest of America maybe it would work better.
Traceroutes provide a snapshot of the route at the time that they are created so intermittent issues may not show up. It may be necessary to run multiple traceroutes or to use a third party program that takes a longer look at the route.
Same issue here, and I am from NC as well. tracert takes a nose dive as soon as it hits the ATT net. Blizzard please help this all happend last year in April please fix.
