Skip to main content
byren's profile

byren

New Contributor

 • 

9 Messages

Closed

connection to blizzard servers...horrible latency

i've had this problem for several weeks now.  i'm quite annoyed at cox saying its blizzard and blizzard saying its cox.  i'm fairly certain i have definitive evidence its a pathing issue which cox (my provider) should step in to help resolve.  

tracert from my local pc:


Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.128.32.1
3 8 ms 8 ms 8 ms 70.169.88.78
4 855 ms 7 ms 7 ms 70.169.88.36
5 8 ms 7 ms 7 ms btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 17 ms 17 ms 17 ms 68.1.2.121
7 68 ms 17 ms 18 ms xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 20 ms 18 ms 17 ms vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
9 * * * Request timed out.
10 18 ms 19 ms 19 ms ATT [4.68.62.230]
11 469 ms 63 ms 51 ms cr2.dlstx.ip.att.net [12.123.16.110]
12 55 ms 55 ms 55 ms cr2.la2ca.ip.att.net [12.122.28.178]
13 51 ms 50 ms 50 ms gar29.la2ca.ip.att.net [12.122.129.241]
14 50 ms 51 ms 51 ms 12.122.251.190
15 51 ms 49 ms 49 ms mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16 50 ms 51 ms 51 ms 12.129.199.178
17 51 ms 51 ms 51 ms 12.129.209.68

Trace complete.

tracert from a remote desktop connection (connected to remote from my local pc):


Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 69.20.12.2
2 1 ms <1 ms <1 ms core7-aggr402a-2.iad3.rackspace.net [69.20.3.112]
3 1 ms <1 ms 1 ms corea-core7.iad2.rackspace.net [69.20.2.96]
4 1 ms <1 ms 1 ms corea-edge7.edge7.iad3.rackspace.net [69.20.1.241]
5 1 ms 1 ms 1 ms xe-2-3-1.er2.dca2.us.above.net [208.185.125.153]
6 <1 ms <1 ms <1 ms vlan52.ebr2.Washington12.Level3.net [4.69.146.222]
7 1 ms 1 ms <1 ms ae-204-3604.edge1.Washington12.Level3.net [4.69.158.45]
8 2 ms 67 ms 1 ms ae1.er1.iad10.us.above.net [64.125.31.206]
9 70 ms 68 ms 3 ms 192.205.36.125
10 70 ms 66 ms 70 ms cr2.dvmco.ip.att.net [12.122.31.85]
11 69 ms 70 ms 67 ms cr2.dvmco.ip.att.net [12.122.31.85]
12 69 ms 68 ms 67 ms cr2.la2ca.ip.att.net [12.122.30.30]
13 66 ms 70 ms 67 ms cr2.la2ca.ip.att.net [12.122.30.30]
14 66 ms 66 ms 66 ms gar20.la2ca.ip.att.net [12.122.128.181]
15 66 ms 66 ms 67 ms 12.122.251.190
16 67 ms 66 ms 67 ms 12.129.209.68

Trace complete.

i put a ticket in last week and the cox rep said 'its blizzards problem' and closed the ticket.  i will open another ticket today but figured id try the forums as well...seems at least some of the posts here get responses.

i have several days worth of tracert files which all have the same issue...the one hop from level3 to the att node (which is actually on level3's backbone) is always 100% packet loss...hence a huge lag spike and resultant frustration.

please help!

Discussions

 • 

Updated 

9.5K

19

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

Where is the latency? The hops at hop 4 and 11 look to be ICMP deprioritization. Notice the latency is back to normal by hope 5 and 11. The second tracet doesn't show any abnormal latency at all. What are you putting the tickets in for? Have you contacted Blizzard?

0

0

B

byren

New Contributor

 • 

9 Messages

if you read the original post you would see the second tracert was from a remote desktop connection not on cox backbone.  again, if youd read the first post you'd see that hop 9 is total packet loss (which is backed up by pathping)...hence latency/lag.  the problem appears to be b/t hops 8 and 10.  yes, i have contacted blizzard but (again if youd read the original post) the difference between my local pc and the remote desktop clearly show this is a cox issue.

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

I don't think the issue is evident in the information posted.  Hop #9 isn't losing any data because you're getting to hop #10 ok.  There may be a benefit to trying without the router to see if there is any difference.

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

byren said:
if you read the original post you would see the second tracert was from a remote desktop connection not on cox backbone.

I did read the original post. Why should it matter where the trace is from if it doesn't show any evidence of the problem? The first trace showed it getting off Cox network within 17ms. The second trace look to be from a trace from a data center on the backbone. Of Course the latency is going to be less, but 17ms is not bad by any means. What are your expectations?

byren said:
again, if youd read the first post you'd see that hop 9 is total packet loss (which is backed up by pathping)

Do you know how ICMP works? How could there be total packet loss at hop 9 and still have a hop 10? Think about it. Please don't insinuate a lack of understanding by me when the lack of understanding appears to be your own

0

0

B

byren

New Contributor

 • 

9 Messages

Health Edge said:

byren said:
if you read the original post you would see the second tracert was from a remote desktop connection not on cox backbone.

I did read the original post. Why should it matter where the trace is from if it doesn't show any evidence of the problem? The first trace showed it getting off Cox network within 17ms. The second trace look to be from a trace from a data center on the backbone. Of Course the latency is going to be less, but 17ms is not bad by any means. What are your expectations?

byren said:
again, if youd read the first post you'd see that hop 9 is total packet loss (which is backed up by pathping)

Do you know how ICMP works? How could there be total packet loss at hop 9 and still have a hop 10? Think about it. Please don't insinuate a lack of understanding by me when the lack of understanding appears to be your own

if you dont insinuate im a liar then i wont insinuate you cant read...you should think about it...if i had 100% understanding, would i be posting asking for help?  and the response i get it some arrogant response...no thank you...please annoy someone else

0

0

B

byren

New Contributor

 • 

9 Messages

ChrisL said:
I don't think the issue is evident in the information posted.  Hop #9 isn't losing any data because you're getting to hop #10 ok.  There may be a benefit to trying without the router to see if there is any difference.

im not at home right now so i cant check, but i know i have the router and modem in one...is there a way to bypass router (iow, can i plug pc directly?).

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

byren said:
if you dont insinuate im a liar then i wont insinuate you cant read.

How did I insinuate you are a liar? I was trying to help and you were rude. The correct response was to apologize, but I see that is beyond you. So now Im not going to try to help you, and since the data provided points to a issue outside Cox, I don't see how Cox can help you. And since only a few of us customers post here, I doubt this thread will get anything but lip service from here on in. 

0

0

B

byren

New Contributor

 • 

9 Messages

Health Edge said:

byren said:
if you dont insinuate im a liar then i wont insinuate you cant read.

How did I insinuate you are a liar? I was trying to help and you were rude. The correct response was to apologize, but I see that is beyond you. So now Im not going to try to help you, and since the data provided points to a issue outside Cox, I don't see how Cox can help you. And since only a few of us customers post here, I doubt this thread will get anything but lip service from here on in. 

your very first statement was 'where is the latency?'...i said i was experiencing latency/lag...you said i was not experiencing what i already said i was experiencing...therefore, you insinuated im a liar...i know what im experiencing...i think you owe me the apology.

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

If you have an all in one bypassing the router definitely won't be an option.  The next best thing you could try is a wired connection if you're not trying that already.

0

0

B

byren

New Contributor

 • 

9 Messages

ChrisL said:
If you have an all in one bypassing the router definitely won't be an option.  The next best thing you could try is a wired connection if you're not trying that already.

direct wired connection to router/modem in one device...

0

0

H

Health_Edge

+5 more

Valued Contributor III

 • 

4.2K Messages

So asking a question is insinuating an answer? You said you were experiencing latency, but your data doesn't show it. I explained how it doesn't show it. The reason I phrased it as "where is the latency" is because I wanted to know what you considered "latency".  I didnt know if you thought 70ms was too high. Or if you thought the ICMP deprioritization was actual packet loss,,,which it turned out you did, so my question was very reasonable. 

0

0

B

byren

New Contributor

 • 

9 Messages

my pathping from 9Apr (im also considering this a pretty clear indicator of packet loss...you tell me):


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 byren_alien [192.168.1.31]
1 192.168.1.1
2 10.128.32.1
3 70.169.88.78
4 70.169.88.36
5 btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 68.1.5.135
7 xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 vlan90.csw4.Dallas1.Level3.net [4.69.145.254]
9 * * *
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 byren_alien [192.168.1.31]
0/ 100 = 0% |
1 73ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 84ms 0/ 100 = 0% 0/ 100 = 0% 10.128.32.1
0/ 100 = 0% |
3 84ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.78
0/ 100 = 0% |
4 84ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.36
0/ 100 = 0% |
5 68ms 0/ 100 = 0% 0/ 100 = 0% btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
0/ 100 = 0% |
6 70ms 0/ 100 = 0% 0/ 100 = 0% 68.1.5.135
0/ 100 = 0% |
7 62ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
0/ 100 = 0% |
8 95ms 0/ 100 = 0% 0/ 100 = 0% vlan90.csw4.Dallas1.Level3.net [4.69.145.254]

Trace complete.

in the final analysis it appears to be an issue with the level3 node (also noted in my original post)...which as i understand it cox pays level3 to route their data.  so, if all that is accurate, i feel cox should contact level3 and put pressure on them to get it fixed.

0

0

B

byren

New Contributor

 • 

9 Messages

pathping from 22Mar:


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 byren_alien [192.168.1.72]
1 192.168.1.1
2 10.128.32.1
3 70.169.88.78
4 70.169.88.36
5 btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 68.1.2.122
7 xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 byren_alien [192.168.1.72]
0/ 100 = 0% |
1 29ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 31ms 0/ 100 = 0% 0/ 100 = 0% 10.128.32.1
0/ 100 = 0% |
3 62ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.78
0/ 100 = 0% |
4 60ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.36
0/ 100 = 0% |
5 74ms 0/ 100 = 0% 0/ 100 = 0% btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 68.1.2.122
0/ 100 = 0% |
7 60ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]

Trace complete.

pathping from 28Mar:


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 byren_alien [192.168.1.72]
1 192.168.1.1
2 10.128.32.1
3 70.169.88.78
4 70.169.88.36
5 btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 68.1.5.135
7 xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 byren_alien [192.168.1.72]
0/ 100 = 0% |
1 64ms 1/ 100 = 1% 1/ 100 = 1% 192.168.1.1
0/ 100 = 0% |
2 86ms 0/ 100 = 0% 0/ 100 = 0% 10.128.32.1
0/ 100 = 0% |
3 77ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.78
0/ 100 = 0% |
4 56ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.36
1/ 100 = 1% |
5 42ms 1/ 100 = 1% 0/ 100 = 0% btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
0/ 100 = 0% |
6 --- 100/ 100 =100% 99/ 100 = 99% 68.1.5.135
0/ 100 = 0% |
7 59ms 1/ 100 = 1% 0/ 100 = 0% xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]

Trace complete.

pathping from 29Mar:


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 byren_alien [192.168.1.15]
1 192.168.1.1
2 10.128.32.1
3 70.169.88.78
4 70.169.88.36
5 btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 68.1.2.122
7 xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 * ae-4-90.ear1.Dallas1.Level3.net [4.69.145.212]
9 ATT [4.68.62.230]
10 cr2.dlstx.ip.att.net [12.123.16.110]
11 cr2.la2ca.ip.att.net [12.122.28.178]
12 gar29.la2ca.ip.att.net [12.122.129.241]
13 12-122-254-238.attens.net [12.122.254.238]
14 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
15 12.129.199.178
16 12.129.209.68

Computing statistics for 400 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 byren_alien [192.168.1.15]
0/ 100 = 0% |
1 78ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 77ms 0/ 100 = 0% 0/ 100 = 0% 10.128.32.1
0/ 100 = 0% |
3 63ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.78
0/ 100 = 0% |
4 62ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.36
0/ 100 = 0% |
5 72ms 0/ 100 = 0% 0/ 100 = 0% btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
0/ 100 = 0% |
6 58ms 0/ 100 = 0% 0/ 100 = 0% 68.1.2.122
0/ 100 = 0% |
7 52ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
0/ 100 = 0% |
8 63ms 0/ 100 = 0% 0/ 100 = 0% ae-4-90.ear1.Dallas1.Level3.net [4.69.145.212]
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% ATT [4.68.62.230]
0/ 100 = 0% |
10 --- 100/ 100 =100% 100/ 100 =100% cr2.dlstx.ip.att.net [12.123.16.110]
0/ 100 = 0% |
11 --- 100/ 100 =100% 100/ 100 =100% cr2.la2ca.ip.att.net [12.122.28.178]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% gar29.la2ca.ip.att.net [12.122.129.241]
0/ 100 = 0% |
13 --- 100/ 100 =100% 100/ 100 =100% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% 12.129.199.178
0/ 100 = 0% |
16 148ms 0/ 100 = 0% 0/ 100 = 0% 12.129.209.68

Trace complete.

pathping from 1Apr:


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 byren_alien [192.168.1.15]
1 192.168.1.1
2 10.128.32.1
3 70.169.88.78
4 70.169.88.36
5 btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 68.1.2.121
7 xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 byren_alien [192.168.1.15]
0/ 100 = 0% |
1 74ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 59ms 0/ 100 = 0% 0/ 100 = 0% 10.128.32.1
0/ 100 = 0% |
3 54ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.78
0/ 100 = 0% |
4 49ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.36
0/ 100 = 0% |
5 44ms 0/ 100 = 0% 0/ 100 = 0% btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 68.1.2.121
0/ 100 = 0% |
7 75ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]

Trace complete.

pathping from 2Apr:


Tracing route to 12.129.209.68 over a maximum of 30 hops

0 byren_alien [192.168.1.15]
1 192.168.1.1
2 10.128.32.1
3 70.169.88.78
4 70.169.88.36
5 btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
6 68.1.2.122
7 xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]
8 * * *
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 byren_alien [192.168.1.15]
0/ 100 = 0% |
1 32ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 52ms 0/ 100 = 0% 0/ 100 = 0% 10.128.32.1
0/ 100 = 0% |
3 68ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.78
0/ 100 = 0% |
4 44ms 0/ 100 = 0% 0/ 100 = 0% 70.169.88.36
0/ 100 = 0% |
5 51ms 0/ 100 = 0% 0/ 100 = 0% btnrdsrj01-so010.0.rd.br.cox.net [68.1.1.217]
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 68.1.2.122
0/ 100 = 0% |
7 48ms 0/ 100 = 0% 0/ 100 = 0% xe-5-0-1.edge5.Dallas3.Level3.net [4.59.32.73]

Trace complete.

0

0

C

ChrisL

Former Moderator

 • 

7.1K Messages

Those results actually don't appear to show loss either.  Keep in mind you're reaching the intended destination without any packet loss.  If you were losing packets along the path in between it would be impossible to reach your intended destination loss free.

0

0

B

byren

New Contributor

 • 

9 Messages

ChrisL said:
Those results actually don't appear to show loss either.  Keep in mind you're reaching the intended destination without any packet loss.  If you were losing packets along the path in between it would be impossible to reach your intended destination loss free.

none of those pathpings reach their destination...the destination IP is 12.129.209.68 ... actually the 29Mar one did actually reach the final IP but none of the others make it past the level3 hop

0

0