Getting extremely High World Latency

Technical Support
Prev 1 5 6 7 25 Next
These traceroute and ping requests are nothing more than stall tactics. There's no reason for anyone to believe that after 5.3 dropped that suddenly our isp began having issues by the hundreds (if not more). Just went from 12ms world and home latency to over 2554ms world and 657ms home latency working on the The Final Power quest. Not in a dungeon, rbg, raid, etc. just out fighting npcs and BOOM.


It is entirely possible for any node between you and Blizzard to be having issues, without Blizzard having direct control over the entire internet. Packet Loss at any type of internet hub is a really common problem in the United States, and tends to impact high performance gaming and things like video streaming that use up a lot of resources - web browsing tends to be less sensitive to packet loss and latency. If the bad hop is only something you encounter when you try to connect to your WOW server, then it could easily only impact you when playing WOW, without Blizzard having direct control over that bad internet hop. The worst part is that bad internet hops can be intermittent, making it really hard to find evidence that there is a problem.

My own WOW raid is having multiple people randomly disconnect during boss fights. The disconnects are so bad (losing 3 or 4 people at a time sometimes) that it prevented us from progressing on heroics this last Thursday. However, in the past, Blizzard server problems would disconnect everyone from the server, not cause casting lag and disconnects for 20% of the raid. Thus, the much more likely cause is an internet hop where the 4 people go through at the same time, but other people in the raid may not be. Blaming Blizzard may be easy, but it doesn't help anything get fixed. Posting data such as traceroutes, however, does help Blizzard have the data they need to be able to pressure AT&T or other internet companies into fixing the problem.

Someone in another thread said:
"A tech has been out and says the following: A DNS server in the middle of the country is having the problem, it's not Comcast, it's not Blizzard, it's

ATT: 12.122.132.241
The packets are getting lost at this address and it's owned by ATT."

http://us.battle.net/wow/en/forum/topic/9245175402?page=2#22

You can run a Pathping to see if that hop is there. IF the problem is between our computers and Blizzard, THEN running the pathping and traceroute programs give Blizzard the evidence they need to put pressure on our service providers. Without data, no one at an internet company is likely to care what Blizzard has to say about another company's internet service. My pathping actually includes the hop that the other poster said might be bad.
Pathping instructions: https://us.battle.net/support/en/article/running-a-pathping-test

Below is my pathping from today, showing that the suspected hop is in my list of hops (underlined for emphasis):

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Gandalph [192.168.1.200]
1 www.asusnetwork.net [192.168.1.1]
2 98.235.72.1
3 te-0-1-0-6-sur01.statecollege.pa.pitt.comcast.net [68.85.43.161]
4 be-3-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.81]
5 c-69-139-168-69.hsd1.nj.comcast.net [69.139.168.69]
6 he-4-13-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.91.185]
7 pos-1-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]
8 192.205.37.33
9 cr1.n54ny.ip.att.net [12.122.131.86]
10 cr2.cgcil.ip.att.net [12.122.1.2]
11 gar6.ipsin.ip.att.net [12.122.132.241]
12 12.122.251.18
13 63.240.130.206
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Gandalph [192.168.1.200]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% www.asusnetwork.net [192.168.1.1]
0/ 100 = 0% |
2 9ms 0/ 100 = 0% 0/ 100 = 0% 98.235.72.1
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% te-0-1-0-6-sur01.statecollege.pa.pitt.comcast.net [68.85.43.161]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% be-3-ar03.lowerpaxton.pa.pitt.comcast.net [69.139.194.81]
0/ 100 = 0% |
5 22ms 0/ 100 = 0% 0/ 100 = 0% c-69-139-168-69.hsd1.nj.comcast.net [69.139.168.69]
0/ 100 = 0% |
6 30ms 0/ 100 = 0% 0/ 100 = 0% he-4-13-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.91.185]
0/ 100 = 0% |
7 31ms 0/ 100 = 0% 0/ 100 = 0% pos-1-1-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.86.46]
0/ 100 = 0% |
8 32ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.33
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.n54ny.ip.att.net [12.122.131.86]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.1.2]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% gar6.ipsin.ip.att.net [12.122.132.241]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.18
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.206

Trace complete.
This is a good summary above. What needs to happen now is for Blizzard to get in touch with the NOC"s at these suspected servers in order to get the ball rolling. For us to continue to call Comcast, Optimum, Cox and other cable networks and for them to tell us, "your service is fine, and signal is fine", is not going to help us. After countless hours, there is no one that I can get on the phone at Comcast that is willing to do investigative work b/c in the end, my signal is very strong and my internet is fine.
But Blizzard, they probably want for my signal to be able to reach them. Someone from Blizzard needs to get on the phone to start talking to the NOC's for ATTnet so that our signals can make it to the game servers.
Since my thread was deleted, and this has some visibility: The way to get Blizzard to put pressure on thier partners is thru the BBB.

https://www.bbb.org/consumer-complaints/file-a-complaint/get-started

Blizzard Entertainment is listed. Every complaint has to be investigated. Might bring attention to this matter from the higher ups.
Since my thread was deleted, and this has some visibility: The way to get Blizzard to put pressure on thier partners is thru the BBB.


This isn't a useful way to solve the problem. There are many different possible causes for disconnect problems, including problems I have seen over the years including:

1) If it is a problem with a bad WOW addon causing game crashes, contacting the BBB can't make Blizzard come fix the addon you installed onto your computer.

2) If it is a problem with the installation of the game on your computer and a file is corrupted causing disconnects, Blizzard can't come in your house and run a repair utility for you.

3) If it is a problem with wireless internet access in someone's house dropping signal, Blizzard can't fix it.

4) If something is wrong with either your modem or router, Blizzard can't fix it.

5) A hardware/software problem on your computer is something Blizzard can't fix. For example, some graphic card drivers have caused problems for people.

6) If water is getting into the internet lines of your house and causing you to disconnect on days that it rains, Blizzard can't fix that either (yes, this caused disconnect problems for someone in my guild once!).

7) If there is something wrong caused by your service provider dropping packets due to a hardware or software problem, that's not something Blizzard can identify or fix either. The best Blizzard can do is collect data from Traceroutes and other postings from players to see if there is a common problem. However, posting on the BBB website instead of posting traceroute data here won't help identify a problem.

8) If there is something wrong caused by packets dropped by a secondary internet service provider other than the one you pay your bills at each month (such as the AT&T hops once your data passes the Comcast hops, for example), then Blizzard can't do much about that without having the traceroutes & other data logs that they have requested.

9) Finally, there could be something on Blizzard's end they could potentially fix. However, potential problems 1 thru 8 (along with other things I can't remember off the top of my head) could also be a problem. Contacting the BBB does absolutely nothing to address any of the possible problems that can lead to disconnects. However, posting the computer diagnostic information can help narrow down what the possible cause might be.
Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:
0 Bunny-PC [192.168.1.3]
1 192.168.1.1
2 c-68-45-112-1.hsd1.nj.comcast.net [68.45.112.1]
3 xe-10-1-0-32767-sur01.turnersville.nj.panjde.comcast.net [68.85.76.177]
4 xe-4-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.63.57]
5 pos-4-1-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.209]
6 pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.87.14]
7 192.205.37.41
8 cr1.wswdc.ip.att.net [12.122.113.42]
9 cr2.sl9mo.ip.att.net [12.122.18.29]
10 cr2.kc9mo.ip.att.net [12.122.28.89]
11 cr1.dlstx.ip.att.net [12.122.28.85]
12 cr1.phmaz.ip.att.net [12.122.28.182]
13 12.123.158.5
14 12-122-254-218.attens.net [12.122.254.218]
15 mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bunny-PC [192.168.1.3]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% c-68-45-112-1.hsd1.nj.comcast.net [68.45.112.1]
0/ 100 = 0% |
3 16ms 0/ 100 = 0% 0/ 100 = 0% xe-10-1-0-32767-sur01.turnersville.nj.panjde.comcast.net [68.85.76.177]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% xe-4-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.63.57]
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% pos-4-1-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.91.209]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.87.14]
0/ 100 = 0% |
7 21ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.41
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.wswdc.ip.att.net [12.122.113.42]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.sl9mo.ip.att.net [12.122.18.29]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.kc9mo.ip.att.net [12.122.28.89]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.28.85]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.phmaz.ip.att.net [12.122.28.182]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12.123.158.5
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-218.attens.net [12.122.254.218]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]

Trace complete.

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 29 ms 23 ms 40 ms c-68-45-112-1.hsd1.nj.comcast.net [68.45.112.1]
3 10 ms 25 ms 23 ms xe-10-1-0-32767-sur01.turnersville.nj.panjde.comcast.net [68.85.76.177]
4 10 ms 9 ms 9 ms xe-4-0-0-0-ar03.audubon.nj.panjde.comcast.net [68.85.63.57]
5 16 ms 31 ms 48 ms pos-3-9-0-0-cr01.ashburn.va.ibone.comcast.net [68.86.95.157]
6 14 ms 13 ms 14 ms pos-0-5-0-0-pe01.ashburn.va.ibone.comcast.net [68.86.87.14]
7 17 ms 20 ms 19 ms 192.205.37.41
8 85 ms 84 ms 81 ms cr1.wswdc.ip.att.net [12.122.113.42]
9 82 ms 83 ms 83 ms cr2.sl9mo.ip.att.net [12.122.18.29]
10 82 ms 83 ms 83 ms cr2.kc9mo.ip.att.net [12.122.28.89]
11 82 ms 88 ms 85 ms cr1.dlstx.ip.att.net [12.122.28.85]
12 88 ms 87 ms 84 ms cr1.phmaz.ip.att.net [12.122.28.182]
13 119 ms 79 ms 166 ms 12.123.158.5
14 79 ms 78 ms 79 ms 12-122-254-218.attens.net [12.122.254.218]
15 78 ms 111 ms 83 ms mdf002c7613r0002-gig-12-1.phx1.attens.net [63.241.130.202]
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.
Actually Lissanna, generally when I have disconnect issues I tend to look at the hand off between internet providers. It's usually at that point where the data loss starts to appear more prevalent. For example in Chelaru's example the issue is when Comcast is handing over the data to AT&T. This isn't always the case but it's the first place I look at and you would need to contact your own internet provider about this issue since there could be maintenance going on on Comcast side that is interfering with the hand off.
Hi there, today playing from a friend's house. Same ISP as me, AT&T Uverse, 16mb FIOS connection.

Currently I am sitting at 29ms / 5880ms world

Here is my tracert, and surprise surprise where the lag is:

1 4 ms 7 ms 3 ms 10.10.10.1
2 23 ms 15 ms 17 ms mpwr-static-208.57.181.1.mpowercom.net [208.57.181.1]
3 53 ms 16 ms 20 ms 208.57.26.129.mpowercom.net [208.57.26.129]
4 28 ms 26 ms 36 ms 4.78.193.9
5 28 ms 21 ms 19 ms ae-26-26.edge6.LosAngeles1.Level3.net [4.69.201.9]
6 52 ms 33 ms 23 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
7 23 ms 19 ms 21 ms ae-73-73.ebr3.LosAngeles1.Level3.net [4.69.137.37]
8 22 ms 30 ms 19 ms ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
9 43 ms 27 ms 19 ms ae-206-3606.bar2.Tustin1.Level3.net [4.69.158.118]
10 30 ms 23 ms 29 ms 192.205.37.145
11 544 ms 541 ms 630 ms cr1.la2ca.ip.att.net [12.122.128.102]
12 219 ms 210 ms 286 ms gar20.la2ca.ip.att.net [12.122.128.181]

13 42 ms 21 ms 28 ms 12-122-254-238.attens.net [12.122.254.238]
14 23 ms 19 ms 18 ms mdf001c7613r0003-gig-12-1.lax1.attens.net [12.129.193.254]
15 * * * Request timed out.

time-outs continue till 30.


Badabing! AT&T!

I have called them several times trying to ask for managers, never getting anyone who knows what I'm talking about. Now that I think of it I know someone in AT&T U-verse tech support management in my guild! LOL I'm gonnna ask him what to do.

He is on now but afk, lol, I will followup shortly,

- Gunnan
This is just lovely. Blizzard supports own page says that that all of those servers are their servers

They say the following:

Because of the safeguards that protect our Battle.net servers, you may notice later hops in your trace route failing with an error message such as 'Request Timed Out' or 'Destination Net Unreachable'. You may also see inflated latency numbers. You can ignore any error messages you receive after contacting our servers as they do not indicate a problem with your internet connection. To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net.

It's at this link at the bottom:

https://us.battle.net/support/en/article/performing-a-traceroute

This is back on Blizzard.
To identify our servers, look for the following suffixes: attens.net, att.net, alter.net, telia.net.


I LOLed irl a lil when i read that...thx Anira :)

- Gunnan
Been having frequent disconnects every day for over a month, with lag spikes becoming more frequent as well, but not as frequent as the d/c's.

I'm not very computer savvy, but here are the traceroute and pathping I ran. I have an iMac.

Traceroute

1 10.0.0.1 (10.0.0.1) 3.893 ms 1.190 ms 1.087 ms
2 dslrouter (192.168.1.1) 2.401 ms 2.311 ms 2.135 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *

Pathping

1 10.0.0.1 (10.0.0.1) 4.017 ms 1.038 ms 1.195 ms 1.224 ms 1.037 ms 1.020 ms 1.005 ms 1.111 ms 1.139 ms 1.101 ms 1.140 ms 1.214 ms 1.167 ms 1.080 ms 1.084 ms 1.051 ms 1.125 ms 3.241 ms 1.545 ms 1.186 ms 1.167 ms 1.067 ms 1.052 ms 1.183 ms 1.103 ms 1.117 ms 1.107 ms 1.165 ms 1.134 ms 1.138 ms (0% loss)
2 dslrouter (192.168.1.1) 3.080 ms 2.345 ms 2.565 ms 2.172 ms 2.248 ms 2.270 ms 3.836 ms 2.260 ms 2.212 ms 2.217 ms 2.290 ms 2.235 ms 2.429 ms 2.245 ms 2.272 ms 2.262 ms 2.282 ms 2.317 ms 2.264 ms 3.714 ms 2.148 ms 2.111 ms 2.177 ms 2.212 ms 2.160 ms 2.174 ms 2.256 ms 2.302 ms 2.316 ms 2.809 ms (0% loss)
3 * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
Arrrggggh, having the same issues as well. I'm getting about 5-6k latency, and even saw it get up to 20k last night. This game is completely unplayable for me right now.


Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Derp-PC [192.168.1.7]
1 192.168.1.1
2 10.130.64.1
3 dtr03jnvlwi-tge-0-6-0-6.jnvl.wi.charter.com [96.34.16.130]
4 crr01ftbgwi-tge-0-1-0-7.ftbg.wi.charter.com [96.34.16.3]
5 crr01euclwi-tge-0-1-0-4.eucl.wi.charter.com [96.34.16.77]
6 bbr01euclwi-tge-0-0-0-2.eucl.wi.charter.com [96.34.2.150]
7 kcm-edge-18.inet.qwest.net [72.164.236.237]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Derp-PC [192.168.1.7]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.130.64.1
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% dtr03jnvlwi-tge-0-6-0-6.jnvl.wi.charter.com [96.34.16.130]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% crr01ftbgwi-tge-0-1-0-7.ftbg.wi.charter.com [96.34.16.3]
0/ 100 = 0% |
5 21ms 1/ 100 = 1% 1/ 100 = 1% crr01euclwi-tge-0-1-0-4.eucl.wi.charter.com [96.34.16.77]
0/ 100 = 0% |
6 25ms 2/ 100 = 2% 2/ 100 = 2% bbr01euclwi-tge-0-0-0-2.eucl.wi.charter.com [96.34.2.150]
0/ 100 = 0% |
7 60ms 0/ 100 = 0% 0/ 100 = 0% kcm-edge-18.inet.qwest.net [72.164.236.237]

Trace complete.



Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 11 ms 11 ms 11 ms 10.130.64.1
3 10 ms 15 ms 11 ms dtr03jnvlwi-tge-0-6-0-6.jnvl.wi.charter.com [96.34.16.130]
4 19 ms 14 ms 15 ms crr01ftbgwi-tge-0-1-0-7.ftbg.wi.charter.com [96.34.16.3]
5 19 ms 20 ms 20 ms crr01euclwi-tge-0-1-0-4.eucl.wi.charter.com [96.34.16.77]
6 24 ms 21 ms 24 ms bbr01euclwi-tge-0-0-0-2.eucl.wi.charter.com [96.34.2.150]
7 92 ms 56 ms 56 ms kcm-edge-18.inet.qwest.net [72.164.236.237]
8 * * * Request timed out.
9 59 ms 57 ms 60 ms 192.205.32.53
10 59 ms 60 ms 59 ms cr1.dlstx.ip.att.net [12.123.18.74]
11 60 ms 74 ms 59 ms cr2.kc9mo.ip.att.net [12.122.28.86]
12 57 ms 78 ms 58 ms cr2.sl9mo.ip.att.net [12.122.28.90]
13 58 ms 57 ms 60 ms cr2.cgcil.ip.att.net [12.122.2.21]
14 55 ms 55 ms 56 ms gar6.ipsin.ip.att.net [12.122.132.241]
15 57 ms 58 ms 60 ms 12.122.251.14
16 81 ms 58 ms 63 ms 63.240.130.202
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.


The concerning part for me in my trace is this:

2 --- 100/ 100 =100% 100/ 100 =100% 10.130.64.1
Renamed the browser exe and everything is fine.
I'm somehow getting about 120ms latency now and am able to play again, but I haven't done anything so I don't know what has changed. I wonder how long this will last...
Here is my info for my random spikes:

5 107.14.19.42
6 ae1.pr1.dca10.tbone.rr.com [107.14.17.202]
7 ix-17-0.tcore2.AEQ-Ashburn.as6453.net [216.6.87.149]
8 192.205.34.245
9 cr2.wswdc.ip.att.net [12.122.84.82]
10 cr1.cgcil.ip.att.net [12.122.18.21]
11 gar18.cgcil.ip.att.net [12.122.99.21]
12 12.122.251.18
13 63.240.130.206
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address

5 53ms 0/ 100 = 0% 0/ 100 = 0% 107.14.19.42
0/ 100 = 0% |
6 53ms 0/ 100 = 0% 0/ 100 = 0% ae1.pr1.dca10.tbone.rr.com [107.14
.17.202]
0/ 100 = 0% |
7 47ms 23/ 100 = 23% 23/ 100 = 23% ix-17-0.tcore2.AEQ-Ashburn.as6453.
net [216.6.87.149]
0/ 100 = 0% |
8 56ms 0/ 100 = 0% 0/ 100 = 0% 192.205.34.245
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.84.82
]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21
]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% gar18.cgcil.ip.att.net [12.122.99.
21]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.18
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.206
Here is my results during a minor lag spike. Points again to AT&T.

0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.38.37.95
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% G0-3-2-6.TAMPFL-LCR-22.verizon-gni.net [130.81.185.84]
0/ 100 = 0% |
4 16ms 0/ 100 = 0% 0/ 100 = 0% so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81.28.214]
0/ 100 = 0% |
5 19ms 0/ 100 = 0% 0/ 100 = 0% 0.ae2.BR1.MIA19.ALTER.NET [152.63.87.178]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% 204.255.168.18
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr81.fldfl.ip.att.net [12.122.82.22]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.ormfl.ip.att.net [12.122.1.45]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.attga.ip.att.net [12.122.5.142]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.1.174]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.wswdc.ip.att.net [12.122.2.33]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.phlpa.ip.att.net [12.122.4.53]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar1.pitpa.ip.att.net [12.122.107.85]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-242.attens.net [12.122.254.242]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]

Trace complete.
Thought I'd toss in my 2¢:

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 dv6 [192.168.1.104]
1 CISCOE4200 [192.168.1.1]
2 host-69-144-102-154.jcs-wy.client.bresnan.net [69.144.102.154]
3 mslmtfh1dr5-GE-3-1-6-U0.int.bresnan.net [69.144.26.18]
4 mslmtfh1cr5-XE-5-0-0-U0.int.bresnan.net [72.175.110.20]
5 seawafh2cr5-XE-4-3-0-U0.int.bresnan.net [72.175.111.20]
6 gltwy001hb2-SE-3-0.int.bresnan.net [69.145.214.134]
7 12.90.77.21
8 cr1.st6wa.ip.att.net [12.123.46.6]
9 cr2.sffca.ip.att.net [12.122.31.194]
10 cr2.la2ca.ip.att.net [12.122.31.133]
11 gar29.la2ca.ip.att.net [12.122.129.241]
12 12.122.251.190
13 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 dv6 [192.168.1.104]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% CISCOE4200 [192.168.1.1]
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% host-69-144-102-154.jcs-wy.client.bresnan.net [69.144.102.154]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% mslmtfh1dr5-GE-3-1-6-U0.int.bresnan.net [69.144.26.18]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% mslmtfh1cr5-XE-5-0-0-U0.int.bresnan.net [72.175.110.20]
0/ 100 = 0% |
5 26ms 0/ 100 = 0% 0/ 100 = 0% seawafh2cr5-XE-4-3-0-U0.int.bresnan.net [72.175.111.20]
0/ 100 = 0% |
6 22ms 0/ 100 = 0% 0/ 100 = 0% gltwy001hb2-SE-3-0.int.bresnan.net [69.145.214.134]
0/ 100 = 0% |
7 34ms 0/ 100 = 0% 0/ 100 = 0% 12.90.77.21
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.st6wa.ip.att.net [12.123.46.6]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.sffca.ip.att.net [12.122.31.194]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.31.133]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]

Trace complete.

**********

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 1 ms 1 ms 3 ms CISCOE4200 [192.168.1.1]
2 6 ms 7 ms 7 ms host-69-144-102-154.jcs-wy.client.bresnan.net [69.144.102.154]
3 12 ms 8 ms 6 ms mslmtfh1dr5-GE-3-1-6-U0.int.bresnan.net [69.144.26.18]
4 9 ms 9 ms 9 ms mslmtfh1cr5-XE-5-0-0-U0.int.bresnan.net [72.175.110.20]
5 20 ms 60 ms 21 ms seawafh2cr5-XE-4-3-0-U0.int.bresnan.net [72.175.111.20]
6 20 ms 41 ms 20 ms gltwy001hb2-SE-3-0.int.bresnan.net [69.145.214.134]
7 19 ms 18 ms 27 ms 12.90.77.21
8 58 ms 59 ms 58 ms cr1.st6wa.ip.att.net [12.123.46.6]
9 60 ms 58 ms 59 ms cr2.sffca.ip.att.net [12.122.31.194]
10 57 ms 58 ms 55 ms cr2.la2ca.ip.att.net [12.122.31.133]
11 58 ms 56 ms 53 ms gar29.la2ca.ip.att.net [12.122.129.241]
12 54 ms 54 ms 56 ms 12-122-254-234.attens.net [12.122.254.234]
13 54 ms 53 ms 55 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
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.
And data run during a crushing lag spike that ended in disconnect.

Pathping
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% 10.38.37.95
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% G0-3-2-6.TAMPFL-LCR-22.verizon-gni.net [130.81.185.84]
0/ 100 = 0% |
4 17ms 0/ 100 = 0% 0/ 100 = 0% so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81.28.214]
0/ 100 = 0% |
5 16ms 2/ 100 = 2% 2/ 100 = 2% 0.ae2.BR1.MIA19.ALTER.NET [152.63.87.178]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% 204.255.168.18
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr81.fldfl.ip.att.net [12.122.82.22]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.ormfl.ip.att.net [12.122.1.45]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.attga.ip.att.net [12.122.5.142]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.1.174]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.wswdc.ip.att.net [12.122.2.33]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr2.phlpa.ip.att.net [12.122.4.53]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar1.pitpa.ip.att.net [12.122.107.85]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.2
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]

Trace complete.
Figured I would bump this thread since I'm also getting high world latency especially during peak hours. I'm located in Atlanta Ga and playing on Ruin Battlegroup (Chicago). Judging from my tracert the problem is coming from 12.122.251.18 which is AT&T owned. Here are my tracert and pathping taken during non peak hours, it only gets worse during peak hours.

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 12 ms 8 ms 10.231.76.1
3 10 ms 13 ms 9 ms dtr01sghlga-tge-0-2-0-17.sghl.ga.charter.com [96.34.78.180]
4 9 ms 10 ms 9 ms crr01sghlga-tge-0-6-0-3.sghl.ga.charter.com [96.34.73.39]
5 15 ms 11 ms 11 ms bbr01atlnga-bue-3.atln.ga.charter.com [96.34.2.70]
6 14 ms 11 ms 10 ms atl-bb1-link.telia.net [80.239.128.161]
7 14 ms 20 ms 10 ms 192.205.33.41
8 54 ms 46 ms 47 ms cr2.attga.ip.att.net [12.122.117.98]
9 46 ms 47 ms 48 ms cr1.nsvtn.ip.att.net [12.122.28.106]
10 49 ms 47 ms 49 ms cr2.nsvtn.ip.att.net [12.122.28.70]
11 51 ms 62 ms 49 ms cr1.cl2oh.ip.att.net [12.122.28.74]
12 51 ms 48 ms 48 ms cr1.cgcil.ip.att.net [12.122.2.205]
13 46 ms 46 ms 46 ms gar18.cgcil.ip.att.net [12.122.99.21]
14 138 ms 200 ms 203 ms 12.122.251.18
15 45 ms 45 ms 45 ms 63.240.130.206
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.

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Dangle [192.168.1.101]
1 192.168.1.1
2 10.231.76.1
3 dtr01sghlga-tge-0-2-0-17.sghl.ga.charter.com [96.34.78.180]
4 crr01sghlga-tge-0-6-0-1.sghl.ga.charter.com [96.34.73.35]
5 bbr01atlnga-bue-3.atln.ga.charter.com [96.34.2.70]
6 atl-bb1-link.telia.net [80.239.128.161]
7 192.205.33.41
8 cr2.attga.ip.att.net [12.122.117.98]
9 cr1.nsvtn.ip.att.net [12.122.28.106]
10 cr2.nsvtn.ip.att.net [12.122.28.70]
11 cr1.cl2oh.ip.att.net [12.122.28.74]
12 cr1.cgcil.ip.att.net [12.122.2.205]
13 gar18.cgcil.ip.att.net [12.122.99.21]
14 12.122.251.18
15 63.240.130.206
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Dangle [192.168.1.101]
0/ 100 = 0% |
1 2ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 --- 100/ 100 =100% 100/ 100 =100% 10.231.76.1
0/ 100 = 0% |
3 10ms 0/ 100 = 0% 0/ 100 = 0% dtr01sghlga-tge-0-2-0-17.sghl.ga.charter.com [96.34.78.180]
0/ 100 = 0% |
4 --- 100/ 100 =100% 100/ 100 =100% crr01sghlga-tge-0-6-0-1.sghl.ga.charter.com [96.34.73.35]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% bbr01atlnga-bue-3.atln.ga.charter.com [96.34.2.70]
0/ 100 = 0% |
6 15ms 0/ 100 = 0% 0/ 100 = 0% atl-bb1-link.telia.net [80.239.128.161]
0/ 100 = 0% |
7 14ms 0/ 100 = 0% 0/ 100 = 0% 192.205.33.41
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.attga.ip.att.net [12.122.117.98]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr1.nsvtn.ip.att.net [12.122.28.106]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr2.nsvtn.ip.att.net [12.122.28.70]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.cl2oh.ip.att.net [12.122.28.74]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.2.205]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar18.cgcil.ip.att.net [12.122.99.21]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.18
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.206

Trace complete.
Not sure if anyone else has been having this problem (I'm using a Uverse setup with a residential gateway for internet and television), but I had a tech come by to look at what the problem may have been and he was of absolute no help. His exact words were, "I don't know what to tell you, my iPad works great with your wifi. It's probably your computer. But you know AT&T doesn't guarantee speeds." The last thing I did to this computer was replace the mobo about 8 months ago. I personally noticed this problem with substantial packet loss yesterday. There is little to no room for any surmountable correlation between the two. I kinda just sat there speechless when the tech told me this and figured I'd mess with it a little today when I got home from work.

Tracerts to the Reckoning battlegroup still saw some substantial packet loss and I finally called AT&T with the intention of cancelling in lieu of Cox. Went through the automated motions and this time the robot asked if it could remotely reset my Uverse television receiver and residential gateway separately. I agreed to the reboot and haven't had any issues in the past hour with rubberbanding, NPCs/mobs disappearing or increased world latency, so I'm beginning to think AT&T is the culprit here.

The odd thing is that I am still receiving packet loss through tracerts to more notable web sites such as google.com and facebook.com, and they always start on hop 3 whereas my connection to Reckoning completely times out after hop 10.

tldr; ISP says it's Blizzard, Blizzard says it's ISP. Same story, different day.

Join the Conversation

Return to Forum