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
New Contributor
•
Packet Loss During Peak Times with Ultimate Tier
I've been experiencing excess packet loss during the evening for the past few weeks. This causes frequent disconnects in online games as well as excess lag.
At around 7:00pm today:
Tracing route to cox.net [68.99.123.161]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 7 ms 8 ms 10.0.16.1
3 7 ms 8 ms 7 ms 68.1.8.229
4 8 ms 13 ms 9 ms 68.1.8.207
5 26 ms 8 ms 9 ms 68.1.8.86
6 16 ms 11 ms 11 ms dukedsrj02-ge210.0.rd.at.cox.net [68.1.1.123]
7 12 ms 30 ms 12 ms 68.1.15.238
8 * 11 ms 10 ms 68.99.123.4
9 12 ms 12 ms 11 ms ww2.cox.com [68.99.123.161]
Trace complete.
C:\Users\Matthew>ping cox.net -t
Pinging cox.net [68.99.123.161] with 32 bytes of data:
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Request timed out.
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=10ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=16ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=13ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=11ms TTL=56
Reply from 68.99.123.161: bytes=32 time=11ms TTL=56
Reply from 68.99.123.161: bytes=32 time=10ms TTL=56
Reply from 68.99.123.161: bytes=32 time=13ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=11ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Request timed out.
Reply from 68.99.123.161: bytes=32 time=10ms TTL=56
Reply from 68.99.123.161: bytes=32 time=11ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=11ms TTL=56
Reply from 68.99.123.161: bytes=32 time=13ms TTL=56
Reply from 68.99.123.161: bytes=32 time=11ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Request timed out.
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=12ms TTL=56
Reply from 68.99.123.161: bytes=32 time=11ms TTL=56
Ping statistics for 68.99.123.161:
Packets: Sent = 34, Received = 31, Lost = 3 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 16ms, Average = 11ms
I also ran PingPlotter against the FFXIV ARR server that I play on as well as on cox.net.
FFXIV ARR - http://imgur.com/nZyC6sV
COX.net - http://imgur.com/ZJm4BmS
I've also uploaded my signal page from my modem (SB6141).
http://imgur.com/eLhW0zA
Trikein
Contributor III
•
Signal levels look good. Upstream power level is borderline but I wouldn't suspect that to cause the symtoms your describing.
All pingplotter tests show a 6-13% packel loss between Hop 1 and 2, with no suspect latency. This leads me to believe it's a wiring or port between modem and router.
Try bypassing, going direct to modem and see if that elviates the problem. To isolate run Pingplotter on 192.168.100.1, as long as that checks out everything on your side is usually good to go.
0
0
cornbreadninja
New Contributor
•
No packet loss when running on 192.168.100.1
http://imgur.com/GgyVMn2
0
0
Trikein
Contributor III
•
Looks like it's intermittent. The packet loss occurred just over 2 seconds in a 2-3min period. Maybe just try a basic Ping via CMD? Ping -t cox.net and Ping -t 192.168.100.1. You should see packet loss on to 192.168.100.1 when ever you see it at cox.net. If not, then I am missing something. Or you can isolate by bypassing the routing and seeing if the problem occurs. Which ever is easiest.
If someone sees something I am missing, please chime in.
0
0
ChrisL
Former Moderator
•
The ping tests seem to show some loss but the trace route didn't seem to catch it at the time it ran. I'd suggest trying the trace route again when the ping tests are confirmed to be experiencing loss to see if we can catch which hop is actually experiencing the loss.
0
0
cornbreadninja
New Contributor
•
Ran the ping tests again at the same time:
Ping statistics for 192.168.100.1:
Packets: Sent = 214, Received = 214, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Ping statistics for 68.99.123.161:
Packets: Sent = 188, Received = 183, Lost = 5 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 16ms, Average = 11ms
Also ran the PingPlotter again:
http://imgur.com/NvRf8Fb
And the cmd line tracert
Tracing route to cox.net [68.99.123.161]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms * 7 ms 10.0.16.1
3 7 ms 7 ms 6 ms 68.1.8.229
4 9 ms 10 ms 9 ms 68.1.8.207
5 8 ms 9 ms 7 ms 68.1.8.86
6 10 ms * 11 ms dukedsrj02-ge210.0.rd.at.cox.net [68.1.1.123]
7 12 ms 11 ms 11 ms 68.1.15.238
8 * * 11 ms 68.99.123.4
9 12 ms 12 ms 11 ms ww2.cox.com [68.99.123.161]
0
0
ChrisL
Former Moderator
•
0
0