Welcome to the Cox Community
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
Messages
Selected Messages
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
New Contributor
•
2 Messages
Closed
I have new service from COX and my speed is otherwise fine, but when I log into World of Warcraft I will have 91 lat [good], 76ms [my connection to them Good] 2253ms [VERY BAD, data loss] I looked on a few forums and they suggested a Tracer, the results suggest packet loss from level3.net, this is not a COX node, so the only thing I can do is request that COX puts in a request to level3.net and have them fix their node.
Tracing route to 12.129.209.68 over a maximum of 30 hops
0 ******-** [192.168.0.2]
1 192.168.0.1
2 10.104.0.1
3 24-234-16-208.ptp.lvcm.net [24.234.16.208]
4 24-234-6-68.ptp.lvcm.net [24.234.6.68]
5 ae54.bar2.LasVegas1.Level3.net [205.129.18.109]
6 ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98]
7 ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98]
8 192.205.37.145
9 cr2.la2ca.ip.att.net [12.122.129.106]
10 12.123.249.73
11 * * *
Computing statistics for 250 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 ******-** [192.168.0.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.104.0.1
0/ 100 = 0% |
3 7ms 0/ 100 = 0% 0/ 100 = 0% 24-234-16-208.ptp.lvcm.net [24.234.16.208]
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% 24-234-6-68.ptp.lvcm.net [24.234.6.68]
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% ae54.bar2.LasVegas1.Level3.net [205.129.18.109]
0/ 100 = 0% |
6 106ms 1/ 100 = 1% 1/ 100 = 1% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98]
0/ 100 = 0% |
7 107ms 1/ 100 = 1% 1/ 100 = 1% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98]
0/ 100 = 0% |
8 107ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.145
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.129.106]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.123.249.73
_______________________________________________________
Tracer for pathping 199.108.62.157 > c:\pathping.txt
5 10ms 0/ 100 = 0% 0/ 100 = 0% ae54.bar2.LasVegas1.Level3.net [205.129.18.109]
0/ 100 = 0% |
6 108ms 1/ 100 = 1% 1/ 100 = 1% ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
0/ 100 = 0% |
7 106ms 0/ 100 = 0% 0/ 100 = 0% ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102]
3/ 100 = 3% |
8 108ms 3/ 100 = 3% 0/ 100 = 0% 192.205.37.145
97/ 100 = 97% |
Discussions
•
Updated
4K
3
0
0
Internet outage 24 hrs
Discussions
4
0
Package site
Discussions
0
0
Daily outages
Discussions
2
0
They don’t care
Discussions
1
0
Billing cycle
Discussions
1
0
Package site
Discussions
0
0
Bills
Discussions
1
0
Internet outage 24 hrs
Discussions
4
0
Jb4201
New Contributor
•
I am having the exact same issue with World of Warcraft.
0
0
Health_Edge
+5 more
Valued Contributor III
•
First, could you go into more detail about when you said " I will have 91 lat [good], 76ms [my connection to them Good] 2253ms [VERY BAD, data loss]"? I understand the 76ms part, but what is lat? Also, I see the latency spike about 100ms, not 2253ms.
Second, for accuracy, here is a tracert from Level3 Tustin to what to closest public IP from your trace; 24.234.16.208. For more, see http://lookingglass.level3.net/
Traceroute results from Tustin, CA to 24.234.16.208(24-234-16-208.ptp.lvcm.net)
1 ae-1-4.bar1.LasVegas1.Level3.net (4.69.133.109) 6.61 ms 6.51 ms 21.8 ms
2 ae-1-4.bar1.LasVegas1.Level3.net (4.69.133.109) 6.66 ms 6.62 ms 6.65 ms
3 4.35.34.214 (4.35.34.214) 7.45 ms 7.31 ms 7.37 ms
4 24-234-6-17.ptp.lvcm.net (24.234.6.17) 97.2 ms 101 ms 97.5 ms
5 24-234-6-69.ptp.lvcm.net (24.234.6.69) 103 ms
5 0.0.0.0 *
5 24-234-6-69.ptp.lvcm.net (24.234.6.69) 99.2 ms
Also, have you tried/thought about setting up a IPv6 tunnel for "possibly" different routing? Check out https://tunnelbroker.net/ They have a server in Los Angeles.
0
0
Anarinola
New Contributor
•
The issue seems to be resolved now.
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.104.0.1
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% 24-234-16-208.ptp.lvcm.net [24.234.16.208]
0/ 100 = 0% |
4 8ms 0/ 100 = 0% 0/ 100 = 0% 24-234-6-68.ptp.lvcm.net [24.234.6.68]
0/ 100 = 0% |
5 11ms 0/ 100 = 0% 0/ 100 = 0% ae54.bar2.LasVegas1.Level3.net [205.129.18.109]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98]
0/ 100 = 0% |
7 17ms 0/ 100 = 0% 0/ 100 = 0% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98]
0/ 100 = 0% |
8 18ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.145
100/ 100 =100%
0
0