New Contributor
•
6 Messages
Significant Packet loss when connecting to Diablo 3 servers.
After submitting a ticket with Blizzard about packet loss issues I was directed to ask for help here since they didn't have any power to help fix the packet loss.
When connecting to their online service at IP 12.129.222.10 I see significant packet loss at 2 nodes (96%+) and slight packet loss on a few others (Less than 4%).
The PathPing for this is below:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 [192.168.0.100]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr1.dlstx.ip.att.net [12.122.85.234]
9 12.123.249.165
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.0.100]
1/ 100 = 1% |
1 6ms 5/ 100 = 5% 4/ 100 = 4% 10.3.36.1
0/ 100 = 0% |
2 8ms 3/ 100 = 3% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 2/ 100 = 2% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 32ms 1/ 100 = 1% 0/ 100 = 0% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 --- 100/ 100 =100% 99/ 100 = 99% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 45ms 1/ 100 = 1% 0/ 100 = 0% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 50ms 1/ 100 = 1% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
99/ 100 = 99% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.85.234]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.165
Trace complete.
Any help to fix this would be greatly appreciated.
Related Content
Closed
1
0
Closed
1
0
Closed
1
0
Closed
2
0
Closed
1
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
" [192.168.0.100] 1/ 100 = 1% |"
Looks like you are getting slight packet loss(1%) on your network, and that packet loss is carrying through the rest of the trace. Not sure if the packet loss is PC to router or router to modem.
Can you bypass the router and do another pathping? Or if you don't want to bypass, and want to isolate, try "ping -n 50 192.168.100.1" and "ping -n 50 192.168.0.100"
Also, what modem and router do you have?
Last, any packet loss to other sites? Like 8.8.8.8 or google.com?
0
0
Ozzy
New Contributor
•
6 Messages
I ran the ping tests as suggested to filter out packet loss locally.
Modem Ping Test:
Ping statistics for 192.168.100.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 13ms, Average = 0ms
Router Ping Test:
Ping statistics for 192.168.0.100:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
More information as follows.
The setup I have is a wired setup through a Cisco DPQ3212 Modem and a D-Link DIR-860L Router.
The issue may not be specific to Diablo 3 as I have noticed YouTube videos sometimes taking a while to buffer. But I am only interested in getting the packet loss fixed for Diablo 3 so I can actually play the game without 800-1200 latency every time I am doing anything besides sitting idle.
The following tests were run with my computer directly connected to the modem, unless otherwise noted. I also power cycled the modem and restarted my computer before running these.
Modem info page before running the following tests:
PathPing to Diablo 3 servers:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr2.dlstx.ip.att.net [12.123.16.78]
9 12.123.249.225
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
0/ 100 = 0% |
1 6ms 1/ 100 = 1% 1/ 100 = 1% 10.3.36.1
0/ 100 = 0% |
2 8ms 2/ 100 = 2% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 8ms 2/ 100 = 2% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 36ms 1/ 100 = 1% 1/ 100 = 1% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 52ms 0/ 100 = 0% 0/ 100 = 0% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
1/ 100 = 1% |
6 59ms 2/ 100 = 2% 1/ 100 = 1% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 49ms 1/ 100 = 1% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
99/ 100 = 99% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.123.16.78]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.225
Trace complete.
Path Ping to Google.com:
Tracing route to www.google.com [2607:f8b0:4007:807::2004]
over a maximum of 30 hops:
0 [2600:8807:9f01:103:ade9:ce32:cb42:ed03]
1 2600:8807:9f01:103::1
2 2001:578:1c00:4::56
3 2001:578:1c00:4::2
4 2001:578:1:0:172:17:248:182
5 2001:4860:1:1:0:58f5:0:1a
6 2001:4860::1:0:dd7
7 2001:4860::8:0:2c9d
8 2001:4860::8:0:7a1a
9 * 2001:4860::1:0:6b02
10 2001:4860:0:1::39d
11 lax17s04-in-x04.1e100.net [2607:f8b0:4007:807::2004]
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [2600:8807:9f01:103:ade9:ce32:cb42:ed03]
0/ 100 = 0% |
1 15ms 0/ 100 = 0% 0/ 100 = 0% 2600:8807:9f01:103::1
0/ 100 = 0% |
2 8ms 4/ 100 = 4% 4/ 100 = 4% 2001:578:1c00:4::56
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 2001:578:1c00:4::2
0/ 100 = 0% |
4 35ms 1/ 100 = 1% 1/ 100 = 1% 2001:578:1:0:172:17:248:182
0/ 100 = 0% |
5 25ms 2/ 100 = 2% 2/ 100 = 2% 2001:4860:1:1:0:58f5:0:1a
0/ 100 = 0% |
6 43ms 1/ 100 = 1% 1/ 100 = 1% 2001:4860::1:0:dd7
0/ 100 = 0% |
7 25ms 1/ 100 = 1% 1/ 100 = 1% 2001:4860::8:0:2c9d
0/ 100 = 0% |
8 66ms 0/ 100 = 0% 0/ 100 = 0% 2001:4860::8:0:7a1a
1/ 100 = 1% |
9 74ms 2/ 100 = 2% 1/ 100 = 1% 2001:4860::1:0:6b02
0/ 100 = 0% |
10 71ms 2/ 100 = 2% 1/ 100 = 1% 2001:4860:0:1::39d
0/ 100 = 0% |
11 59ms 1/ 100 = 1% 0/ 100 = 0% lax17s04-in-x04.1e100.net [2607:f8b0:4007:807::2004]
Trace complete.
Path Ping to North American League of Legends Servers: *Note: In game I experience no latency above 52 and no random spikes at all.
Tracing route to 104.160.131.1 over a maximum of 30 hops
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
5 72.215.224.162
6 104.160.133.35
7 ae36-br01.chi01.riotdirect.net [104.160.159.66]
8 104.160.131.1
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 10.3.36.1
1/ 100 = 1% |
2 8ms 2/ 100 = 2% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 1/ 100 = 1% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 --- 100/ 100 =100% 99/ 100 = 99% langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
0/ 100 = 0% |
5 --- 100/ 100 =100% 99/ 100 = 99% 72.215.224.162
0/ 100 = 0% |
6 --- 100/ 100 =100% 99/ 100 = 99% 104.160.133.35
0/ 100 = 0% |
7 --- 100/ 100 =100% 99/ 100 = 99% ae36-br01.chi01.riotdirect.net [104.160.159.66]
0/ 100 = 0% |
8 75ms 1/ 100 = 1% 0/ 100 = 0% 104.160.131.1
Trace complete.
Path Ping to YouTube.com:
Tracing route to youtube-ui.l.google.com [2607:f8b0:4002:c07::5b]
over a maximum of 30 hops:
0 [2600:8807:9f01:103:ade9:ce32:cb42:ed03]
1 2600:8807:9f01:103::1
2 2001:578:1c00:4::56
3 2001:578:1c00:4::2
4 2001:578:1:0:172:17:248:182
5 2001:4860:1:1:0:58f5:0:1a
6 2001:4860::1:0:57f
7 2001:4860::8:0:64bf
8 2001:4860::8:0:8ed9
9 2001:4860::2:0:878c
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [2600:8807:9f01:103:ade9:ce32:cb42:ed03]
0/ 100 = 0% |
1 13ms 0/ 100 = 0% 0/ 100 = 0% 2600:8807:9f01:103::1
0/ 100 = 0% |
2 7ms 2/ 100 = 2% 2/ 100 = 2% 2001:578:1c00:4::56
0/ 100 = 0% |
3 --- 100/ 100 =100% 100/ 100 =100% 2001:578:1c00:4::2
0/ 100 = 0% |
4 35ms 0/ 100 = 0% 0/ 100 = 0% 2001:578:1:0:172:17:248:182
0/ 100 = 0% |
5 25ms 2/ 100 = 2% 2/ 100 = 2% 2001:4860:1:1:0:58f5:0:1a
0/ 100 = 0% |
6 46ms 2/ 100 = 2% 2/ 100 = 2% 2001:4860::1:0:57f
0/ 100 = 0% |
7 24ms 1/ 100 = 1% 1/ 100 = 1% 2001:4860::8:0:64bf
0/ 100 = 0% |
8 52ms 1/ 100 = 1% 1/ 100 = 1% 2001:4860::8:0:8ed9
0/ 100 = 0% |
9 64ms 0/ 100 = 0% 0/ 100 = 0% 2001:4860::2:0:878c
Trace complete.
Path Ping to Amazon.com:
Tracing route to www.amazon.com [54.239.25.192]
over a maximum of 30 hops:
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 72.21.221.202
6 176.32.125.210
7 176.32.125.217
8 54.240.229.0
9 54.240.229.160
10 54.240.228.135
11 54.239.108.112
12 54.239.109.41
13 205.251.245.174
14 * * *
Computing statistics for 325 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
0/ 100 = 0% |
1 7ms 0/ 100 = 0% 0/ 100 = 0% 10.3.36.1
0/ 100 = 0% |
2 9ms 3/ 100 = 3% 3/ 100 = 3% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 38ms 3/ 100 = 3% 3/ 100 = 3% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 49ms 0/ 100 = 0% 0/ 100 = 0% 72.21.221.202
0/ 100 = 0% |
6 --- 100/ 100 =100% 100/ 100 =100% 176.32.125.210
0/ 100 = 0% |
7 --- 100/ 100 =100% 100/ 100 =100% 176.32.125.217
0/ 100 = 0% |
8 --- 100/ 100 =100% 100/ 100 =100% 54.240.229.0
0/ 100 = 0% |
9 --- 100/ 100 =100% 100/ 100 =100% 54.240.229.160
0/ 100 = 0% |
10 62ms 0/ 100 = 0% 0/ 100 = 0% 54.240.228.135
1/ 100 = 1% |
11 --- 100/ 100 =100% 99/ 100 = 99% 54.239.108.112
0/ 100 = 0% |
12 48ms 1/ 100 = 1% 0/ 100 = 0% 54.239.109.41
75/ 100 = 75% |
13 59ms 76/ 100 = 76% 0/ 100 = 0% 205.251.245.174
Trace complete.
Path Ping to Google DNS 8.8.8.8:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 * 72.14.212.233
6 216.239.50.93
7 64.233.174.69
8 google-public-dns-a.google.com [8.8.8.8]
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
1/ 100 = 1% |
1 6ms 1/ 100 = 1% 0/ 100 = 0% 10.3.36.1
0/ 100 = 0% |
2 8ms 3/ 100 = 3% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 8ms 1/ 100 = 1% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 37ms 1/ 100 = 1% 0/ 100 = 0% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
1/ 100 = 1% |
5 45ms 2/ 100 = 2% 0/ 100 = 0% 72.14.212.233
0/ 100 = 0% |
6 --- 100/ 100 =100% 98/ 100 = 98% 216.239.50.93
0/ 100 = 0% |
7 --- 100/ 100 =100% 98/ 100 = 98% 64.233.174.69
0/ 100 = 0% |
8 37ms 2/ 100 = 2% 0/ 100 = 0% google-public-dns-a.google.com [8.8.8.8]
Trace complete.
Path Ping to Cox.com:
Tracing route to www.cox.com [68.99.123.161]
over a maximum of 30 hops:
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
5 68.1.15.234
6 68.99.123.4
7 ww2.cox.com [68.99.123.161]
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
0/ 100 = 0% |
1 7ms 4/ 100 = 4% 4/ 100 = 4% 10.3.36.1
0/ 100 = 0% |
2 8ms 2/ 100 = 2% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 1/ 100 = 1% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 38ms 0/ 100 = 0% 0/ 100 = 0% dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
0/ 100 = 0% |
5 30ms 0/ 100 = 0% 0/ 100 = 0% 68.1.15.234
0/ 100 = 0% |
6 31ms 2/ 100 = 2% 2/ 100 = 2% 68.99.123.4
0/ 100 = 0% |
7 50ms 0/ 100 = 0% 0/ 100 = 0% ww2.cox.com [68.99.123.161]
Trace complete.
Ping Tests I also ran during this time:
http://www.pingtest.net/result/138146018.png
http://www.pingtest.net/result/138146077.png
http://www.pingtest.net/result/138145874.png
http://www.pingtest.net/result/138145834.png
http://www.pingtest.net/result/138145769.png
http://www.pingtest.net/result/138145717.png
Ping Tests I ran after putting my router back in place:
http://www.pingtest.net/result/138147848.png
http://www.pingtest.net/result/138147895.png
http://www.pingtest.net/result/138148264.png
http://www.pingtest.net/result/138148296.png
http://www.pingtest.net/result/138147940.png
http://www.pingtest.net/result/138148193.png
http://www.pingtest.net/result/138148345.png
http://www.pingtest.net/result/138148433.png
http://www.pingtest.net/result/138148935.png
Lastly one more Path Ping to Diablo 3 servers with the router back in place:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 [192.168.0.100]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr1.dlstx.ip.att.net [12.122.85.234]
9 12.123.249.165
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.0.100]
0/ 100 = 0% |
1 7ms 0/ 100 = 0% 0/ 100 = 0% 10.3.36.1
0/ 100 = 0% |
2 9ms 3/ 100 = 3% 3/ 100 = 3% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 33ms 2/ 100 = 2% 2/ 100 = 2% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 58ms 3/ 100 = 3% 3/ 100 = 3% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 80ms 0/ 100 = 0% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.85.234]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.165
Trace complete.
As I stated before, it isn’t anything on my end or Diablo 3’s end that is causing the latency/packet loss. I have talked to their support and they directed me to contact my ISP (Cox) since the packet loss is happening at nodes on the router to and from their servers.
0
0
ChrisL
Former Moderator
•
7.1K Messages
When I look from this end I'm immediately seeing what looks like a router that may not be suitable to handle the speeds you're in billing for. However based on your test results this may be a secondary issue. I'm seeing no packet loss between us and the modem, that combined with your packet loss being shown with and without the router leads me to believe it may be originating at the PC itself. Can you try testing with a different PC and see what your results look like?
0
0
Ozzy
New Contributor
•
6 Messages
The router I have, as stated above is a D-Link DIR-850L AC 1200 Mbps Gigabit Router. It should be fine for the package I have.
Here is a speed test with it connected: http://www.speedtest.net/result/5014448333.png
Here is a speed test bypassing the router later in the evening: http://www.speedtest.net/result/5015415562.png
Having said that I believe there has been some miscommunication. I was not asking about the packet loss between me and any of the Cox nodes. But asking for Cox to contact ntt.net on my behalf since they won’t talk with end users and only ISP’s, as ntt.net’s nodes are the ones causing a ton of packet loss for me trying to reach Diablo 3 servers.
And having said that after looking at 50+ different tests and a few different tools while directly connected to the modem and bypassing the router, it seems like this may be a slightly larger scope issue than I thought.
The signals today before tests:
The test below was done on the only other computer in the house, a ~2008 Vista Desktop with an old cisco wireless dongle for connection --PathPing to Diablo 3 servers:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 [192.168.0.101]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr1.dlstx.ip.att.net [12.122.85.234]
9 12.123.249.165
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.0.101]
1/ 100 = 1% |
1 33ms 2/ 100 = 2% 1/ 100 = 1% 10.3.36.1
0/ 100 = 0% |
2 28ms 1/ 100 = 1% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 41ms 2/ 100 = 2% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 74ms 1/ 100 = 1% 0/ 100 = 0% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
1/ 100 = 1% |
5 --- 100/ 100 =100% 98/ 100 = 98% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 70ms 2/ 100 = 2% 0/ 100 = 0% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 86ms 2/ 100 = 2% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
98/ 100 = 98% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.85.234]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.165
Trace complete.
Hop’s 6 and 7 were the ones I was concerned with, as they showed a lot of packet loss for Diablo 3’s servers and I assumed that was the cause of the lag.
Assuming my network adapter may had been faulty, I uninstalled the drivers and installed the newest ones manually, and performed more tests, they are as follows, and are when bypassing the router and directly connecting to the modem.
PathPing to Diablo 3 servers:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 [192.168.0.100]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr1.dlstx.ip.att.net [12.122.85.234]
9 12.123.249.165
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.0.100]
1/ 100 = 1% |
1 6ms 1/ 100 = 1% 0/ 100 = 0% 10.3.36.1
0/ 100 = 0% |
2 9ms 3/ 100 = 3% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 1/ 100 = 1% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 32ms 2/ 100 = 2% 1/ 100 = 1% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 --- 100/ 100 =100% 99/ 100 = 99% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 45ms 1/ 100 = 1% 0/ 100 = 0% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 50ms 1/ 100 = 1% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
99/ 100 = 99% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.85.234]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.165
Trace complete.
Another PathPing to Diablo 3 servers done 5 hours later at roughly 10:15pm:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr2.dlstx.ip.att.net [12.123.16.78]
9 12.123.249.225
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
0/ 100 = 0% |
1 6ms 2/ 100 = 2% 2/ 100 = 2% 10.3.36.1
0/ 100 = 0% |
2 8ms 1/ 100 = 1% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 37ms 0/ 100 = 0% 0/ 100 = 0% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
1/ 100 = 1% |
5 71ms 2/ 100 = 2% 1/ 100 = 1% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 89ms 2/ 100 = 2% 1/ 100 = 1% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 73ms 1/ 100 = 1% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
99/ 100 = 99% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.123.16.78]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.225
Trace complete.
PathPing to Cox.com:
Tracing route to www.cox.com [68.99.123.161]
over a maximum of 30 hops:
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
5 68.1.15.234
6 68.99.123.4
7 ww2.cox.com [68.99.123.161]
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
0/ 100 = 0% |
1 6ms 2/ 100 = 2% 2/ 100 = 2% 10.3.36.1
0/ 100 = 0% |
2 8ms 2/ 100 = 2% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 8ms 2/ 100 = 2% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 37ms 1/ 100 = 1% 1/ 100 = 1% dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
0/ 100 = 0% |
5 30ms 0/ 100 = 0% 0/ 100 = 0% 68.1.15.234
1/ 100 = 1% |
6 31ms 2/ 100 = 2% 1/ 100 = 1% 68.99.123.4
0/ 100 = 0% |
7 49ms 1/ 100 = 1% 0/ 100 = 0% ww2.cox.com [68.99.123.161]
Trace complete.
PathPing to GulfPower.com (I assumed this would be fairly close location wise and would have no packet loss):
Tracing route to gulfpower.com [146.126.56.132]
over a maximum of 30 hops:
0 [edited to remove]
1 10.3.36.1
2 ip68-1-11-214.at.at.cox.net [68.1.11.214]
3 ip68-1-11-214.at.at.cox.net [68.1.11.214]
4 maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
5 ae58.edge1.Atlanta4.Level3.net [4.53.232.57]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [edited to remove]
0/ 100 = 0% |
1 7ms 4/ 100 = 4% 4/ 100 = 4% 10.3.36.1
0/ 100 = 0% |
2 11ms 4/ 100 = 4% 4/ 100 = 4% ip68-1-11-214.at.at.cox.net [68.1.11.214]
0/ 100 = 0% |
3 12ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-214.at.at.cox.net [68.1.11.214]
100/ 100 =100% |
4 --- 100/ 100 =100% 0/ 100 = 0% maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
0/ 100 = 0% |
5 --- 100/ 100 =100% 0/ 100 = 0% ae58.edge1.Atlanta4.Level3.net [4.53.232.57]
Trace complete.
WinMTR to Cox.com:
WinMTR statistics
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|---------------------------------------------------------|---------|-------|-------|------|---------|------|
| 10.3.36.1 - 2 | 1172 | 1159 | 5 | 8 | 69 | 5 |
| ip68-1-11-212.at.at.cox.net - 2 | 1176 | 1164 | 6 | 9 | 48 | 8 |
| ip68-1-11-212.at.at.cox.net - 2 | 1156 | 1139 | 6 | 9 | 67 | 12 |
| dukedsrj01-ae4.0.rd.at.cox.net - 2 | 1152 | 1134 | 47 | 50 | 83 | 51 |
| 68.1.15.234 - 2 | 1136 | 1114 | 48 | 51 | 103 | 52 |
| 68.99.123.4 - 6 | 1016 | 964 | 48 | 51 | 82 | 50 |
| ww2.cox.com - 2 | 1160 | 1144 | 48 | 51 | 91 | 50 |
WinMTR to League of Legends servers:
WinMTR statistics
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------------------|--------|---------|------|--------|-------|-------|
| 10.3.36.1 - 2 | 1055 | 1038 | 5 | 8 | 39 | 13 |
| ip68-1-11-212.at.at.cox.net - 2 | 1075 | 1063 | 6 | 10 | 56 | 10 |
| ip68-1-11-212.at.at.cox.net - 2 | 1051 | 1033 | 6 | 9 | 56 | 8 |
| langbprj01-ae7.0.rd.la.cox.net - 2 | 1055 | 1038 | 58 | 62 | 148 | 60 |
| 72.215.224.162 - 2 | 1055 | 1038 | 72 | 75 | 149 | 76 |
| 104.160.133.35 - 2 | 1059 | 1043 | 88 | 92 | 136 | 92 |
| ae36-br01.chi01.riotdirect.net - 1 | 1091 | 1083 | 72 | 75 | 133 | 75 |
| 104.160.131.1 - 4 | 987 | 953 | 85 | 89 | 113 | 87 |
WinMTR to Diablo 3 servers:
WinMTR statistics
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|-------------------------------------------------------------|--------|--------|-------|-------|--------|-------|
| 10.3.36.1 - 2 | 1303 | 1286 | 5 | 8 | 40 | 6 |
| ip68-1-11-212.at.at.cox.net - 2 | 1283 | 1261 | 6 | 10 | 45 | 11 |
| ip68-1-11-212.at.at.cox.net - 2 | 1295 | 1276 | 6 | 9 | 54 | 7 |
| dalsbprj01-ae1.0.rd.dl.cox.net - 2 | 1271 | 1246 | 35 | 38 | 77 | 39 |
| ae-12.r08.dllstx09.us.bb.gin.ntt.net - 1 | 1323 | 1311 | 36 | 39 | 83 | 37 |
| ae-5.r01.dllstx04.us.bb.gin.ntt.net - 3 | 1267 | 1241 | 45 | 48 | 101 | 47 |
| ae-0.att.dllstx04.us.bb.gin.ntt.net - 2 | 1295 | 1276 | 44 | 49 | 109 | 45 |
| cr2.dlstx.ip.att.net - 2 | 1287 | 1266 | 44 | 49 | 99 | 48 |
| 12.123.249.225 - 1 | 1323 | 1311 | 38 | 41 | 97 | 39 |
Ping Tests Tonight:
http://www.pingtest.net/result/138225496.png – Dallas, Tx 2% Packet loss, 63 ms Ping, 27 ms Jitter
http://www.pingtest.net/result/138225617.png - Chicago, Il 1% Packet Loss, 71 ms Ping, 26 ms Jitter
http://www.pingtest.net/result/138225690.png - Lynnwood, Wa 1% Packet Loss, 163 ms Ping, 84 ms Jitter
http://www.pingtest.net/result/138225809.png - Los Angeles, Ca 2% Packet Loss, 58 ms Ping, 3 ms Jitter
http://www.pingtest.net/result/138225870.png - Orlando, Fl 0% Packet Loss, 103 ms Ping, 101ms Jitter
3 month old League of Legends network log analysis - at this time I had zero issues in game, no lag, no spikes, nothing:
Yesterday's League of Legends network log analysis - again, no issues in game at all with ping, lag spikes, etc:
Ping Plotter I ran to Diablo 3 Servers:
With all of that, I have a few questions. Could the modem be responsible for all of my headaches? I noticed the more I tested tonight the more it seemed like the hop with IP 10.3.36.1 was having more and more packet loss issues, and I am assuming that's the modem. If this does seem like an issue with the modem, could I take it to the Cox solutions store tomorrow when I go, and have it exchanged? Next question is why do hop 2 and 3 in the above PathPing tests have the same IP address and is that something that is normal?
Thanks for your help.
0
0
ChrisL
Former Moderator
•
7.1K Messages
Any issues with the destination network provider would be up to the gaming host to work out as how we have no relationship with them. Based on the results you've provided however I'm still thinking the problem is the PC and not the Internet connection. Can you try those results with a different PC connected directly to the modem and see what you get?
0
0
Ozzy
New Contributor
•
6 Messages
While I realize it would be their responsibility to provide support on their end, the packet loss I keep talking about happens before their ATT network starts. The packet loss in the pathping’s that I was focused on was at hop 6 and 7 on the NTT.NET network, hop 5 is the hop where the trace leaves cox’s network and goes to NTT’s, NTT controls hop 5-7 and hop 8 it leaves NTT and joins ATT’s/Blizzard’s local network to their servers. But I can’t contact NTT directly as they won’t deal with end users, only the ISP’s that are using their networks. That is why I made the post here.
Quoting the Tech Support response from Blizzard:
“Tech Specialist Paronharth here.
I checked into this and it looks like all of the packet loss on this Pathping is on the connection that your internet service provider is giving you to our servers. We aren't able to make any kind of changes to connections outside of our servers, but your internet service provider actually has the power over your connectoin path between your modem and our servers.
If you get in touch with your internet service provider and let them know *specifically* that your connection is having trouble connecting to an online service at the IP 12.129.222.10 and show them this Pathping that's measuring the packet loss on the 1st, 2nd, 3rd, 4th, 6th, and 7th nodes then they should be able to help out with this.”
The PathPing he is referring to is the one listed below from 1/18:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 [192.168.0.100]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr1.dlstx.ip.att.net [12.122.85.234]
9 12.123.249.165
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 [192.168.0.100]
1/ 100 = 1% |
1 6ms 5/ 100 = 5% 4/ 100 = 4% 10.3.36.1
0/ 100 = 0% |
2 8ms 3/ 100 = 3% 2/ 100 = 2% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 2/ 100 = 2% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 32ms 1/ 100 = 1% 0/ 100 = 0% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 --- 100/ 100 =100% 99/ 100 = 99% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 45ms 1/ 100 = 1% 0/ 100 = 0% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 50ms 1/ 100 = 1% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
99/ 100 = 99% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.dlstx.ip.att.net [12.122.85.234]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.165
Trace complete.
With that out of the way, you asked me to run the same tests from another computer using a wired connection directly to the modem, and they are here below.
Signal Screen before starting tests:
PathPing to Diablo 3 servers:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 Secondary PC
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr2.dlstx.ip.att.net [12.123.16.78]
9 12.123.249.221
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Secondary PC
0/ 100 = 0% |
1 7ms 0/ 100 = 0% 0/ 100 = 0% 10.3.36.1
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 33ms 5/ 100 = 5% 5/ 100 = 5% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 --- 100/ 100 =100% 100/ 100 =100% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 41ms 1/ 100 = 1% 1/ 100 = 1% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 51ms 0/ 100 = 0% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.123.16.78]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.221
Trace complete.
PathPing to League of Legends Servers:
Tracing route to 104.160.131.1 over a maximum of 30 hops
0 Secondary PC
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
5 72.215.224.162
6 104.160.133.35
7 ae36-br01.chi01.riotdirect.net [104.160.159.66]
8 104.160.131.1
Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Secondary PC
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 10.3.36.1
1/ 100 = 1% |
2 7ms 2/ 100 = 2% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 8ms 1/ 100 = 1% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
1/ 100 = 1% |
4 --- 100/ 100 =100% 98/ 100 = 98% langbprj01-ae7.0.rd.la.cox.net [68.1.0.149]
0/ 100 = 0% |
5 --- 100/ 100 =100% 98/ 100 = 98% 72.215.224.162
0/ 100 = 0% |
6 --- 100/ 100 =100% 98/ 100 = 98% 104.160.133.35
0/ 100 = 0% |
7 --- 100/ 100 =100% 98/ 100 = 98% ae36-br01.chi01.riotdirect.net [104.160.159.66]
0/ 100 = 0% |
8 76ms 2/ 100 = 2% 0/ 100 = 0% 104.160.131.1
Trace complete.
PathPing to Google.com
Tracing route to ya-in-f147.1e100.net [173.194.219.147]
over a maximum of 30 hops:
0 Secondary PC
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 72.14.212.233
6 209.85.244.122
7 66.249.95.198
8 209.85.142.118
9 209.85.143.205
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Secondary PC
0/ 100 = 0% |
1 6ms 2/ 100 = 2% 2/ 100 = 2% 10.3.36.1
0/ 100 = 0% |
2 8ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 32ms 1/ 100 = 1% 1/ 100 = 1% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 46ms 0/ 100 = 0% 0/ 100 = 0% 72.14.212.233
5/ 100 = 5% |
6 49ms 5/ 100 = 5% 0/ 100 = 0% 209.85.244.122
95/ 100 = 95% |
7 --- 100/ 100 =100% 0/ 100 = 0% 66.249.95.198
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% 209.85.142.118
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 209.85.143.205
Trace complete.
Pathping to gulfpower.com:
Tracing route to gulfpower.com [146.126.88.132]
over a maximum of 30 hops:
0 Secondary PC
1 10.3.36.1
2 ip68-1-11-214.at.at.cox.net [68.1.11.214]
3 ip68-1-11-214.at.at.cox.net [68.1.11.214]
4 maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
5 ae58.edge1.Atlanta4.Level3.net [4.53.232.57]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Secondary PC
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 10.3.36.1
1/ 100 = 1% |
2 10ms 2/ 100 = 2% 1/ 100 = 1% ip68-1-11-214.at.at.cox.net [68.1.11.214]
0/ 100 = 0% |
3 10ms 1/ 100 = 1% 0/ 100 = 0% ip68-1-11-214.at.at.cox.net [68.1.11.214]
99/ 100 = 99% |
4 --- 100/ 100 =100% 0/ 100 = 0% maribprj01-ae1.0.rd.at.cox.net [68.1.0.41]
0/ 100 = 0% |
5 --- 100/ 100 =100% 0/ 100 = 0% ae58.edge1.Atlanta4.Level3.net [4.53.232.57]
Trace complete.
Still assuming 10.3.36.1 is the modem, and seeing as how it had been having packet loss, pinging it resulted in the following:
Ping statistics for 10.3.36.1:
Packets: Sent = 250, Received = 249, Lost = 1 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 20ms, Average = 6ms
Ping Tests:
http://www.pingtest.net/result/138261999.png Lynnwood, Wa 0% packet loss 158 ms ping 44 ms jitter
http://www.pingtest.net/result/138261953.png Chicago, Il 1% packet loss 66 ms ping 1 ms jitter
http://www.pingtest.net/result/138261904.png Dallas, Tx 2% packet loss 52 ms ping 27 ms jitter
http://www.pingtest.net/result/138261857.png Los Angeles, Ca 2% packet loss 73 ms ping 4 ms jitter
http://www.pingtest.net/result/138261796.png Orlando, Fl 1% packet loss 58 ms ping 13 ms jitter
Ping Plotter to D3 servers over 10 minutes:
All tests above were done mid-day in a secondary computer with a wired connection directly to the modem.
The tests below were early this morning around 8:30, from my primary computer, wired directly to the modem, these tests were to see how things looked at not-peak times.
Pathping to cox.com:
Tracing route to www.cox.com [68.99.123.161]
over a maximum of 30 hops:
0 Primary PC
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
5 68.1.15.234
6 68.99.123.4
7 ww2.cox.com [68.99.123.161]
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Primary PC
0/ 100 = 0% |
1 6ms 1/ 100 = 1% 1/ 100 = 1% 10.3.36.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 9ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 37ms 0/ 100 = 0% 0/ 100 = 0% dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
0/ 100 = 0% |
5 29ms 0/ 100 = 0% 0/ 100 = 0% 68.1.15.234
0/ 100 = 0% |
6 30ms 0/ 100 = 0% 0/ 100 = 0% 68.99.123.4
1/ 100 = 1% |
7 49ms 1/ 100 = 1% 0/ 100 = 0% ww2.cox.com [68.99.123.161]
Trace complete.
Pathping to Diablo 3 servers:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 Primary PC
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr2.dlstx.ip.att.net [12.123.16.78]
9 12.123.249.225
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Primary PC
0/ 100 = 0% |
1 6ms 0/ 100 = 0% 0/ 100 = 0% 10.3.36.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% ip68-1-11-212.at.at.cox.net [68.1.11.212]
1/ 100 = 1% |
3 7ms 2/ 100 = 2% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 35ms 2/ 100 = 2% 1/ 100 = 1% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 51ms 3/ 100 = 3% 2/ 100 = 2% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 59ms 1/ 100 = 1% 0/ 100 = 0% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 47ms 1/ 100 = 1% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
99/ 100 = 99% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.123.16.78]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.225
Trace complete.
Ping Plotter from my Primary PC over 1 hour, shortly after completing the tests with the Secondary PC:
Also again, I am concerned by hop 2 and 3 having the same IP, is that some sort of network loop that shouldn't be there?
Thanks again for your help
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
Looks like latency spikes between router and modem. Notice spikes and jitter in Pathping. Even at hop 1 with router bypassed. I also see some slight peer congestion, but I would suggest troubleshooting that first. Replace ethernet between modem and router? Also, is it CAT6? Are you using same ethernet to test PC>Modem as PC>Router>Modem?
Congestion at Cox network. Looks like ICMP depriozation is kicking in too, but shouldn't be packet loss. What is your upload speed like?
0
0
Ozzy
New Contributor
•
6 Messages
It's a CAT6 Ethernet cable, I have changed it since I noticed issues. I use the same cable to test both, I just swap it from PC>Router to PC>Modem and back.
http://www.speedtest.net/result/5018275643.png Upload speed looks OK @ 8.22 Mb/s currently.
Pinging the modem again with the router in place gives these results:
Ping statistics for 192.168.100.1:
Packets: Sent = 500, Received = 500, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 48ms, Average = 0ms
1 ping at 48 ms, 1 at 10 ms, 1 at 5 ms, 1 at 4 ms, 1 at 3 ms. The rest are >1 ms.
0
0
Tecknowhelp
Valued Contributor II
•
2.8K Messages
Try ping -n 50 127.0.0.1. If there is ANY packet loss or latency above 1ms there is a issue with the NIC. If not, either a issue with the ethernet, or ethernet connection on modem. If you just see the first ping lag, that is probably just a OS fluke.
Also, what tier do you have? Looks like maxing out at 100Mbps.
0
0
Ozzy
New Contributor
•
6 Messages
Today seemed different. The Link light on the modem is orange, and the signals after the rain last night seem… bad. I have the ‘Cox High-Speed Internet - Premier Package’ which if I remember correctly is 100 down/10 up?
SpeedTest: http://www.speedtest.net/result/5019250874.png
And one from Cox's Website:
Here’s the ping test you wanted me to do.
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
Pathping to Cox.com this morning since I haven’t been able to do one off peak hours:
Tracing route to cox.com [68.99.123.161]
over a maximum of 30 hops:
0 Primary PC [98.170.205.16]
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
5 68.1.15.234
6 68.99.123.4
7 ww2.cox.com [68.99.123.161]
Computing statistics for 175 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Primary PC
0/ 100 = 0% |
1 14ms 3/ 100 = 3% 3/ 100 = 3% 10.3.36.1
0/ 100 = 0% |
2 14ms 1/ 100 = 1% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 15ms 1/ 100 = 1% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 44ms 0/ 100 = 0% 0/ 100 = 0% dukedsrj01-ae4.0.rd.at.cox.net [68.1.1.121]
0/ 100 = 0% |
5 36ms 1/ 100 = 1% 1/ 100 = 1% 68.1.15.234
0/ 100 = 0% |
6 38ms 0/ 100 = 0% 0/ 100 = 0% 68.99.123.4
1/ 100 = 1% |
7 57ms 1/ 100 = 1% 0/ 100 = 0% ww2.cox.com [68.99.123.161]
Trace complete.
One to Diablo 3 servers this morning as well:
Tracing route to 12.129.222.10 over a maximum of 30 hops
0 Primary PC
1 10.3.36.1
2 ip68-1-11-212.at.at.cox.net [68.1.11.212]
3 ip68-1-11-212.at.at.cox.net [68.1.11.212]
4 dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
5 ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
6 ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
7 ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
8 cr2.dlstx.ip.att.net [12.123.16.78]
9 12.123.249.225
10 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Primary PC
0/ 100 = 0% |
1 6ms 1/ 100 = 1% 1/ 100 = 1% 10.3.36.1
0/ 100 = 0% |
2 8ms 1/ 100 = 1% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
3 8ms 1/ 100 = 1% 1/ 100 = 1% ip68-1-11-212.at.at.cox.net [68.1.11.212]
0/ 100 = 0% |
4 34ms 1/ 100 = 1% 1/ 100 = 1% dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109]
0/ 100 = 0% |
5 51ms 2/ 100 = 2% 2/ 100 = 2% ae-12.r08.dllstx09.us.bb.gin.ntt.net [129.250.194.173]
0/ 100 = 0% |
6 59ms 1/ 100 = 1% 1/ 100 = 1% ae-5.r01.dllstx04.us.bb.gin.ntt.net [129.250.3.233]
0/ 100 = 0% |
7 58ms 0/ 100 = 0% 0/ 100 = 0% ae-0.att.dllstx04.us.bb.gin.ntt.net [129.250.8.238]
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.dlstx.ip.att.net [12.123.16.78]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.225
Trace complete.
These were all done bypassing the router and directly connecting to the modem, having said that hop 1 with the IP of 10.3.36.1 is the modem in this case, correct? If it’s having random amounts of packet loss between 0-5%, shouldn’t that show it’s an issue with the modem and that it needs to be replaced? I asked the other day but I don’t believe I ever got a response. Also it’s still strange seeing hop 2 and 3 have the same IP.
Thanks again for your help.
0
0
ChrisL
Former Moderator
•
7.1K Messages
The orange link light is consistent with some of the problems I've been seeing here indicating some sort of problem within the home network. The modem is a possibility however you might benefit from having a technician come take a look.
0
0