Lag on Proudmoore

Hey guys,

Hopefully someone can point me in the right direction with this. A little backstory.

On Tuesday (release day) I logged in and had no issues aside from slowdown due to the amount of people on my screen. :-) No biggie. I was still able to proceed through the opening area of Pandaria. I kept saying to myself, this has got to be the first expansion where there hasn't been any huge problems on launch day! It was a total breeze.

Come to Wednesday... got on in the morning, everything was working fine. Then the rolling restarts came. After the restarts I started to notice a little higher latency but I was still able to play. However towards 3:00pm EST the game became unplayable because the lag was so incredibly bad. I decided that it was going through an adjustment period and stopped playing for the day.

Now it's Thursday. Logged on this morning and lag is still making the game unplayable. The monitor ingame shows Home Latency @ 2211 and World Latency @ 4637.

I've done my due diligence on my end. I've disabled addons, I've shut down everything in the background, made sure all drivers were up to date, dusted out my box, etc. I also contacted DirecPath (ISP) to see if there was any issue on their end, which of course they are saying there isn't a problem on their end. I provided them with the following tracert (copied below) and I would tend to agree that the issue isn't on their side of things.

Suggestions?

Fal

Tracing route to 12.129.254.168 over a maximum of 30 hops

1 1 ms <1 ms 1 ms z65-182-57-1.ips.direcpath.com [65.182.57.1]
2 1 ms <1 ms <1 ms 172.24.2.116
3 <1 ms <1 ms 1 ms 172.24.0.246
4 <1 ms <1 ms 7 ms xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
5 57 ms 48 ms 75 ms 192.205.35.233
6 50 ms 51 ms 52 ms cr1.attga.ip.att.net [12.123.22.26]
7 52 ms 51 ms 51 ms cr2.dlstx.ip.att.net [12.122.28.174]
8 51 ms 52 ms 54 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 90 ms 112 ms 48 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 49 ms 54 ms 49 ms 12-122-254-238.attens.net [12.122.254.238]
11 50 ms 50 ms 50 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Reply Quote
Sorry for the bump but it seems that the people on Tichcondrius think their problems are way more important that everyone else's and feel the need to post 20 identical posts. So just wanted to push my issue that may be affecting others back up instead of flooding the board.

Thank you.
Reply Quote
Any blue love for me? :-)
Reply Quote
Support Forum Agent
Hey Falshir,

If you continue to see high home and world latency after the rolling restarts in 10 minutes, we'll go forward with troubleshooting.
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'
Reply Quote
Things are a TAD better, but not much. Still more delay in casting then there should be.

Home Latency is showing at 46 (much better)
World Latency is still very high at 1686.

I've posted a new tracert to the same IP address. It still looks like the issue is after it gets outside of my ISP. Any help would be appreciated.

Tracing route to 12.129.254.168 over a maximum of 30 hops

1 1 ms <1 ms 1 ms z65-182-57-1.ips.direcpath.com [65.182.57.1]
2 1 ms <1 ms <1 ms 172.24.2.116
3 10 ms 199 ms 199 ms 172.24.0.246
4 <1 ms <1 ms <1 ms xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
5 1 ms <1 ms 1 ms 192.205.35.233
6 51 ms 51 ms 50 ms cr1.attga.ip.att.net [12.123.22.26]
7 50 ms 51 ms 54 ms cr2.dlstx.ip.att.net [12.122.28.174]
8 53 ms 52 ms 50 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 49 ms 50 ms 48 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 49 ms 50 ms 50 ms 12-122-254-234.attens.net [12.122.254.234]
11 50 ms 50 ms 50 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Reply Quote
Support Forum Agent
Can you run a pathping? That will take several minutes, but will show more detail.
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'
Reply Quote
Here are the results of the pathping. Let me know if I can provide anything else.

Tracing route to 12.129.254.168 over a maximum of 30 hops

0 Christopher-PC.direcpath.net [65.182.57.225]
1 z65-182-57-1.ips.direcpath.com [65.182.57.1]
2 172.24.2.116
3 172.24.0.246
4 xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
5 192.205.35.233
6 cr1.attga.ip.att.net [12.123.22.26]
7 cr2.dlstx.ip.att.net [12.122.28.174]
8 cr2.la2ca.ip.att.net [12.122.28.178]
9 gar29.la2ca.ip.att.net [12.122.129.241]
10 12-122-254-238.attens.net [12.122.254.238]
11 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Christopher-PC.direcpath.net [65.182.57.225]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% z65-182-57-1.ips.direcpath.com [65.182.57.1]
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 172.24.2.116
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% 172.24.0.246
0/ 100 = 0% |
4 2ms 0/ 100 = 0% 0/ 100 = 0% xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
0/ 100 = 0% |
5 4ms 0/ 100 = 0% 0/ 100 = 0% 192.205.35.233
100/ 100 =100% |
6 --- 100/ 100 =100% 0/ 100 = 0% cr1.attga.ip.att.net [12.123.22.26]
0/ 100 = 0% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.122.28.174]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.
Edited by Velnrak on 9/28/2012 10:50 AM PDT
Reply Quote
Can I provide anything else aside from this pathping? I'd love to know what needs to happen to correct the lag issues.
Reply Quote
90 Night Elf Priest
6420
Hello!

I too am having high latency problems on Proudmoore (/wave Falshir!). I began to notice it just after the launch of MoP, and with the exception of a couple of brief periods of low latency, it has been persistent. As I type this, home latency is 4632 and world latency is 2117.

I have removed all addons, deleted the Cache, Interface, and WTF folders, performed an ipconfig DNS flush, upgraded my video drivers, and a few other things suggested to me when I opened a ticket, and nothing has changed. The person I was in contact with suggested leaving a message here if the problem persisted, so here I am! I should note that I am experiencing this on both my desktop computer and laptop.

Here are the results of a tracert and pathping:

Tracert:

Tracing route to 12.129.254.168 over a maximum of 30 hops

1 12 ms 7 ms 14 ms 184.66.8.1
2 31 ms 19 ms 13 ms 64.59.163.66
3 9 ms 11 ms 12 ms rd2cv-pos1-0.gv.shawcable.net [66.163.72.6]
4 16 ms 27 ms 29 ms rc3wt-ge10-0-0.wa.shawcable.net [66.163.76.217]
5 12 ms 27 ms 12 ms ethernet11-2.ar6.sea1.gblx.net [209.130.172.85]
6 51 ms 105 ms 78 ms po5-40G.ar3.LAX2.gblx.net [67.16.141.170]
7 41 ms 40 ms 52 ms 192.205.34.73
8 43 ms 43 ms 44 ms cr2.la2ca.ip.att.net [12.122.129.98]
9 40 ms 39 ms 39 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 230 ms 86 ms 169 ms 12-122-254-238.attens.net [12.122.254.238]
11 39 ms 49 ms 41 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Pathping:

Tracing route to 12.129.254.168 over a maximum of 30 hops
1 184.66.8.1
2 64.59.163.66
3 rd2cv-pos1-0.gv.shawcable.net [66.163.72.6]
4 rc3wt-ge10-0-0.wa.shawcable.net [66.163.76.217]
5 ethernet11-2.ar6.sea1.gblx.net [209.130.172.85]
6 po5-40G.ar3.LAX2.gblx.net [67.16.141.170]
7 192.205.34.73
8 cr2.la2ca.ip.att.net [12.122.129.98]
9 gar29.la2ca.ip.att.net [12.122.129.241]
10 12-122-254-234.attens.net [12.122.254.234]
11 mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
1 14ms 0/ 100 = 0% 0/ 100 = 0% 184.66.8.1
0/ 100 = 0% |
2 16ms 0/ 100 = 0% 0/ 100 = 0% 64.59.163.66
0/ 100 = 0% |
3 15ms 0/ 100 = 0% 0/ 100 = 0% rd2cv-pos1-0.gv.shawcable.net [66.163.72.6]
0/ 100 = 0% |
4 19ms 0/ 100 = 0% 0/ 100 = 0% rc3wt-ge10-0-0.wa.shawcable.net [66.163.76.217]
0/ 100 = 0% |
5 25ms 0/ 100 = 0% 0/ 100 = 0% ethernet11-2.ar6.sea1.gblx.net [209.130.172.85]
0/ 100 = 0% |
6 50ms 0/ 100 = 0% 0/ 100 = 0% po5-40G.ar3.LAX2.gblx.net [67.16.141.170]
0/ 100 = 0% |
7 43ms 0/ 100 = 0% 0/ 100 = 0% 192.205.34.73
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.129.98]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]

Trace complete.


Thanks for any help you might be able to provide with this. I understand that there will always be wrinkles after a major expansion, but I'm getting quite frustrated with how unplayable the game is for me right now.

Cheers!
Edited by Velnrak on 9/28/2012 10:51 AM PDT
Reply Quote
Glad I have some company on this!! :-)

Hopefully the blues will be able to give us some more info today.
Reply Quote
A quick update on my end. When I logged on this morning around 7:30am I had very low latency! World and Home gauges were at 75 or below. However, around 8:00, I have now spiked back up to 2533 - Home and 546 - World. So I got about 30 minutes of good unlagged gameplay.

What's going on??? Please help. Attached are tracert and pathpings from around 8:30am EST.

Tracert:

Tracing route to 12.129.254.168 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms z65-182-57-1.ips.direcpath.com [65.182.57.1]
2 <1 ms <1 ms 1 ms 172.24.2.116
3 <1 ms <1 ms <1 ms 172.24.0.246
4 1 ms <1 ms 1 ms xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
5 3 ms <1 ms <1 ms 192.205.35.233
6 54 ms 50 ms 51 ms cr1.attga.ip.att.net [12.123.22.26]
7 52 ms 51 ms 52 ms cr2.dlstx.ip.att.net [12.122.28.174]
8 55 ms 54 ms 50 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 49 ms 48 ms 50 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 49 ms 50 ms 50 ms 12-122-254-234.attens.net [12.122.254.234]
11 49 ms 50 ms 50 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Pathping:

Tracing route to 12.129.24.168 over a maximum of 30 hops

0 Christopher-PC.direcpath.net [65.182.57.225]
1 z65-182-57-1.ips.direcpath.com [65.182.57.1]
2 172.24.2.116
3 172.24.0.246
4 xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
5 192.205.35.233
6 cr2.attga.ip.att.net [12.123.22.154]
7 cr1.nsvtn.ip.att.net [12.122.28.106]
8 cr2.dvmco.ip.att.net [12.122.31.90]
9 cr2.st6wa.ip.att.net [12.122.1.78]
10 cr1.cgcil.ip.att.net [12.122.2.205]
11 cr2.cgcil.ip.att.net [12.122.2.54]
12 12.122.251.110
13 mdf1-bi8k-1-eth-1-4.sea1.attens.net [12.129.1.202]
14 gar8.st6wa.ip.att.net [12.122.111.73]
15 12.122.251.110
16 * * mdf1-bi8k-1-eth-1-4.sea1.attens.net [12.129.1.202]
17 * * *
Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Christopher-PC.direcpath.net [65.182.57.225]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% z65-182-57-1.ips.direcpath.com [65.182.57.1]
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 172.24.2.116
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% 172.24.0.246
0/ 100 = 0% |
4 3ms 0/ 100 = 0% 0/ 100 = 0% xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
0/ 100 = 0% |
5 3ms 0/ 100 = 0% 0/ 100 = 0% 192.205.35.233
100/ 100 =100% |
6 --- 100/ 100 =100% 0/ 100 = 0% cr2.attga.ip.att.net [12.123.22.154]
0/ 100 = 0% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.nsvtn.ip.att.net [12.122.28.106]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.90]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.st6wa.ip.att.net [12.122.1.78]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.2.205]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.2.54]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.110
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% mdf1-bi8k-1-eth-1-4.sea1.attens.net [12.129.1.202]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% gar8.st6wa.ip.att.net [12.122.111.73]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.110
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% mdf1-bi8k-1-eth-1-4.sea1.attens.net [12.129.1.202]

Trace complete.
Edited by Velnrak on 9/28/2012 10:52 AM PDT
Reply Quote
85 Troll Warrior
5055
It's a global issue seems in US and also in some parts of SE asia and Austraila

DO NOT try and fix things on your computer house etc it is a network issue affecting a lot of people but I want to save you from bad customer support that will tell you to do ridiculous things like reinstall, go and check ports, etc.

DONT LISTEN!!!

Just wait and hope they fix it and keep on bumping
Reply Quote
Yeah, I know there is nothing on my end that is wrong. It's obvious from the reports I've provided. I just want to know what is being done to resolve the issue.

Hopefully we'll get another blue response today since I haven't gotten one since I provided the pathpings that the last blue requested.
Reply Quote
90 Human Death Knight
3975
As Troglodyted said, it must be a problem on their end. I've been having the same lag issues- 4k ms, et al- on Rexxar, and it seems to be their communication with parts of the outside world. My guildies aren't experiencing the same lag issues. I'm on the east coast, and my fellow guildies are on the west coast. So, hopefully something can be done as it's pretty frustrating trying to fish and whatnot.
Edited by Sydelus on 9/28/2012 10:46 AM PDT
Reply Quote
Hey Blizz!

Not sure if this helps at all, but the last 2 days, I have had REALLY LOW latency.

However... just this morning, BAM.. back up in to the thousands for home and world!!!!

What happened?

-Fal
Reply Quote
Well after 4 days of no lag... it's back again and greater than ever....

OVER 10,000 on home and 500 on world!!!!

C'mon blizz! What's going on and why does this problem keep popping up?
Reply Quote
Support Forum Agent
Your last traces look good. Have you taken any this morning, when the latency was so high?
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'
Reply Quote
Here is the current tracert and pathpings. It doesn't look like they ever get to the Proudmoore server (12.129.254.168)

Tracert:

Tracing route to 12.129.254.168 over a maximum of 30 hops

1 2 ms <1 ms 1 ms z65-182-57-1.ips.direcpath.com [65.182.57.1]
2 1 ms <1 ms 1 ms 172.24.2.116
3 1 ms <1 ms 1 ms 172.24.0.246
4 <1 ms 1 ms 1 ms xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
5 1 ms 1 ms 1 ms 192.205.35.233
6 53 ms 50 ms 54 ms cr1.attga.ip.att.net [12.123.22.26]
7 51 ms 53 ms 53 ms cr2.dlstx.ip.att.net [12.122.28.174]
8 52 ms 52 ms 54 ms cr2.la2ca.ip.att.net [12.122.28.178]
9 48 ms 49 ms 48 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 50 ms 49 ms 50 ms 12-122-254-238.attens.net [12.122.254.238]
11 75 ms 50 ms 49 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.


Pathping:

Tracing route to 12.129.254.168 over a maximum of 30 hops

0 Christopher-PC.direcpath.net [65.182.57.225]
1 z65-182-57-1.ips.direcpath.com [65.182.57.1]
2 172.24.2.116
3 172.24.0.246
4 xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
5 192.205.35.233
6 cr1.attga.ip.att.net [12.123.22.26]
7 cr2.dlstx.ip.att.net [12.122.28.174]
8 cr2.la2ca.ip.att.net [12.122.28.178]
9 gar29.la2ca.ip.att.net [12.122.129.241]
10 12-122-254-238.attens.net [12.122.254.238]
11 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Christopher-PC.direcpath.net [65.182.57.225]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% z65-182-57-1.ips.direcpath.com [65.182.57.1]
0/ 100 = 0% |
2 0ms 0/ 100 = 0% 0/ 100 = 0% 172.24.2.116
0/ 100 = 0% |
3 14ms 0/ 100 = 0% 0/ 100 = 0% 172.24.0.246
0/ 100 = 0% |
4 3ms 0/ 100 = 0% 0/ 100 = 0% xe-3-1-1.mpr4.atl6.us.above.net [64.125.175.237]
0/ 100 = 0% |
5 4ms 0/ 100 = 0% 0/ 100 = 0% 192.205.35.233
100/ 100 =100% |
6 --- 100/ 100 =100% 0/ 100 = 0% cr1.attga.ip.att.net [12.123.22.26]
0/ 100 = 0% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.122.28.174]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.
Edited by Velnrak on 10/5/2012 2:01 PM PDT
Reply Quote
Support Forum Agent
Those look good — the timeouts at the end are normal. We've our network to not respond to traces. How's your latency right now?
________________________________________________
Technical Support
http://us.battle.net/support
'Constant change is here to stay.'
Reply Quote
90 Human Mage
0
Seems to start at the same time every day for me. 1:30 PDT

Seems that it stopped at 2:00 PDT for me.

Maybe AT&T does something to their database at that time.
Edited by Hikuro on 10/5/2012 2:26 PM PDT
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]