Forum Discussion
- ChrisLFormer Moderator
This appears to be related to the peering issue Blizzard is investigating between Cogento and AT&T. If you have trace route data to post I can confirm this for you.
- raven0816New Contributor
ok here is the pathping without WoW running... ill do another once it is up and running
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Users\Bill>pathping 63.240.161.189
Tracing route to 63.240.161.189 over a maximum of 30 hops
0 Bill-PC [192.168.1.4]
1 192.168.1.1
2 10.38.144.1
3 172.21.0.112
4 70.169.73.90
5 chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 68.1.5.139
7 te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 te0-1-0-1.ccr22.lax01.atlas.cogentco.com [130.117.50.89]
9 te0-1-0-3.ccr22.iah01.atlas.cogentco.com [154.54.44.253]
10 te0-0-0-6.ccr22.dfw01.atlas.cogentco.com [154.54.3.177]
11 te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
12 te0-3-0-7.ccr22.ord01.atlas.cogentco.com [154.54.84.78]
13 te0-5-0-3.ccr22.ord03.atlas.cogentco.com [154.54.43.234]
14 192.205.37.173
15 cr2.cgcil.ip.att.net [12.122.84.94]
16 gar3.cgcil.ip.att.net [12.122.132.213]
17 12.122.251.22
18 63.240.130.214
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bill-PC [192.168.1.4]
0/ 100 = 0% |
1 5ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 22ms 0/ 100 = 0% 0/ 100 = 0% 10.38.144.1
0/ 100 = 0% |
3 17ms 1/ 100 = 1% 1/ 100 = 1% 172.21.0.112
0/ 100 = 0% |
4 26ms 0/ 100 = 0% 0/ 100 = 0% 70.169.73.90
0/ 100 = 0% |
5 21ms 0/ 100 = 0% 0/ 100 = 0% chnddsrj01-ae2.0.rd.ph.cox.net [70
.169.76.229]
0/ 100 = 0% |
6 34ms 0/ 100 = 0% 0/ 100 = 0% 68.1.5.139
0/ 100 = 0% |
7 28ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-21.ccr22.lax05.atlas.cogen
tco.com [38.104.84.13]
0/ 100 = 0% |
8 33ms 0/ 100 = 0% 0/ 100 = 0% te0-1-0-1.ccr22.lax01.atlas.cogent
co.com [130.117.50.89]
0/ 100 = 0% |
9 65ms 0/ 100 = 0% 0/ 100 = 0% te0-1-0-3.ccr22.iah01.atlas.cogent
co.com [154.54.44.253]
0/ 100 = 0% |
10 72ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-6.ccr22.dfw01.atlas.cogent
co.com [154.54.3.177]
0/ 100 = 0% |
11 81ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-6.ccr22.mci01.atlas.cogent
co.com [154.54.2.230]
0/ 100 = 0% |
12 91ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-7.ccr22.ord01.atlas.cogent
co.com [154.54.84.78]
0/ 100 = 0% |
13 90ms 0/ 100 = 0% 0/ 100 = 0% te0-5-0-3.ccr22.ord03.atlas.cogent
co.com [154.54.43.234]
0/ 100 = 0% |
14 92ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.173
100/ 100 =100% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.84.94
]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att.net [12.122.132.
213]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.22
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214Trace complete.
C:\Users\Bill>
- raven0816New Contributor
and heres a pathping (tracert... same thing) with wow up and running..
bliz has confirmed that since cox is my isp and responsible for rerouting my traffic it falls on cox not blizzard, cogento or att...
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Users\Bill>pathping 63.240.161.189
Tracing route to 63.240.161.189 over a maximum of 30 hops
0 Bill-PC [192.168.1.4]
1 192.168.1.1
2 10.38.144.1
3 172.21.0.112
4 70.169.73.90
5 chnddsrj01-ae2.0.rd.ph.cox.net [70.169.76.229]
6 * 68.1.5.139
7 te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.104.84.13]
8 te0-3-0-5.ccr22.lax01.atlas.cogentco.com [154.54.44.133]
9 te0-2-0-3.mpd22.iah01.atlas.cogentco.com [154.54.45.9]
10 te0-3-0-2.ccr22.dfw01.atlas.cogentco.com [154.54.0.202]
11 te0-2-0-6.ccr22.mci01.atlas.cogentco.com [154.54.2.230]
12 te0-3-0-7.ccr22.ord01.atlas.cogentco.com [154.54.84.78]
13 te0-5-0-3.ccr22.ord03.atlas.cogentco.com [154.54.43.234]
14 192.205.37.173
15 cr2.cgcil.ip.att.net [12.122.84.94]
16 gar3.cgcil.ip.att.net [12.122.132.213]
17 12.122.251.22
18 63.240.130.214
19 * * *
Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bill-PC [192.168.1.4]
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 13ms 0/ 100 = 0% 0/ 100 = 0% 10.38.144.1
0/ 100 = 0% |
3 14ms 2/ 100 = 2% 2/ 100 = 2% 172.21.0.112
0/ 100 = 0% |
4 22ms 1/ 100 = 1% 1/ 100 = 1% 70.169.73.90
0/ 100 = 0% |
5 15ms 0/ 100 = 0% 0/ 100 = 0% chnddsrj01-ae2.0.rd.ph.cox.net [70
.169.76.229]
0/ 100 = 0% |
6 31ms 0/ 100 = 0% 0/ 100 = 0% 68.1.5.139
0/ 100 = 0% |
7 27ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-21.ccr22.lax05.atlas.cogen
tco.com [38.104.84.13]
0/ 100 = 0% |
8 26ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-5.ccr22.lax01.atlas.cogent
co.com [154.54.44.133]
0/ 100 = 0% |
9 66ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-3.mpd22.iah01.atlas.cogent
co.com [154.54.45.9]
0/ 100 = 0% |
10 68ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-2.ccr22.dfw01.atlas.cogent
co.com [154.54.0.202]
0/ 100 = 0% |
11 76ms 0/ 100 = 0% 0/ 100 = 0% te0-2-0-6.ccr22.mci01.atlas.cogent
co.com [154.54.2.230]
0/ 100 = 0% |
12 87ms 0/ 100 = 0% 0/ 100 = 0% te0-3-0-7.ccr22.ord01.atlas.cogent
co.com [154.54.84.78]
0/ 100 = 0% |
13 89ms 0/ 100 = 0% 0/ 100 = 0% te0-5-0-3.ccr22.ord03.atlas.cogent
co.com [154.54.43.234]
0/ 100 = 0% |
14 92ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.173
100/ 100 =100% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.cgcil.ip.att.net [12.122.84.94
]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% gar3.cgcil.ip.att.net [12.122.132.
213]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.22
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214Trace complete.
C:\Users\Bill>
it seems there is a latency spike during hops 3 and 4... neither one is at cogento or att yet
- ChrisLFormer Moderator
It seems likely your issue may not be related to the issue others are experiencing. T'he data you posted suggests a problem closer to home. Can you try without the router and post your results for us to see?
- warhippyNew Contributor
Chris, In another thread in this forum, when a customer pointed out high latency starting at node four, you stated that latency was not an indicator of the problem, that packet loss was what you were looking for. Look at hop 14 on the last pathping, for that matter, all of them, 100% packet loss. The pathping I submitted in a different thread, 13% packet loss, at the same IP address, the gateway into the Cogentco bottleneck. You can't use one lame excuse in one thread and turn around and use the opposite lame excuse in a different thread.
- ChrisLFormer Moderator
I took a look again at the pathping posted above my last post at hop 14 as you indicated. I'm not sure I understand what you're seeing there. That hop is on AT&T's network and with all subsequent hops not replying I can only speculate this is part of AT&T/Blizzard's network which has been obscured for security reasons.
- warhippyNew Contributor
To me it's saying 100 packets lost/100 packets sent /100%failure. on the other world of warcraft thread, I submitted a pathping that had alot better transfer, it only lost 13 packets out of 100 sent, but that caused the next node to just fail 100%. That isn't a Cox node , but it damned sure is a problem, one that Cox doesn't seem to want to address.
- warhippyNew Contributor
And to add to my last post, google that IP address, you'll find latency problems dating back to 2010. If thats not the problem then why don't you explain the problem, and don't say it's blizzard's fault because century customers are having no latency problems at all. And this problem is happening in guild wars 2 and rift, two other online games not even associated with blizzard, same node, mostly Cox customers
- ChrisLFormer Moderator
Referencing that same pathping above the Cox network stops at hop 6 after which traffic passes to Cogento.
- JAZMNew Contributor
I also am one of the many Cox.net customers who are experiencing extreme latency issues while playing World of Warcraft. According to support forums on the WoW forums Southern AZ customers of Cox.net are the ones who are mainly experiencing these high latency problems. No one seems to want to help people with these problems. I have spoken to Cox tech support and followed their suggestions but Cox.net will not admit that there is a problem between Cogent/ATT routes (I'm probably not using the best terminology here). Here is a tracert I did a while ago.
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Owner>tracert us.logon.battle.net
Tracing route to us.logon.battle.net [12.129.206.130]
over a maximum of 30 hops:
1 7 ms 20 ms 11 ms 10.54.96.1
2 12 ms 7 ms 13 ms 172.21.0.160
3 11 ms 14 ms 14 ms chndcorc01-pos--0-3-0-0.ph.ph.cox.net [70.169.72
.48]
4 10 ms 21 ms 12 ms 70.169.75.153
5 * 23 ms * langbprj02-ae2.rd.la.cox.net [68.1.1.19]
6 22 ms 25 ms 28 ms te0-0-0-21.ccr22.lax05.atlas.cogentco.com [38.10
4.84.13]
7 66 ms 58 ms 58 ms 192.205.37.157
8 73 ms 68 ms 64 ms cr2.la2ca.ip.att.net [12.122.84.218]
9 62 ms 60 ms 63 ms gar29.la2ca.ip.att.net [12.122.129.241]
10 87 ms 66 ms 64 ms 12-122-254-234.attens.net [12.122.254.234]
11 63 ms 60 ms 59 ms 206.16.68.46
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.I will add a link to a Blizzard (World of Warcraft) support forum that details the severity of this problem
I hope you can help us. LOTS of Cox.net customers (including 3 members of my family) play World of Warcraft and have been having this problem for over 3 weeks now.