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
•
Latency Spikes
Every since I got Cox service I have noticed issues in the consistency of my connection. Lately I have taken the liberty of running some pings tests while idling and while doing various activities. I noticed that every 30 seconds - 1 min, or so, that my response while time will jump from about 17-28 ms to 1400-3600 ms. This happens while I am doing nothing on the network and while I am doing my various activities. During the same time this spikes occur I am seeing lag in the various things I am doing. It has made trying to do anything online with my friends near impossible and I do not feel like paying for a service that does not meet my expectations. What can be done to resolve this?
ChrisL
Former Moderator
•
0
0
cpierce
New Contributor
•
What would be the best way to do a trace route for you to look at?
0
0
cpierce
New Contributor
•
This is a trace I did for a game I play. I have researched the issue and later in the trace the request times out for security. I have included the important portion. I did a few and some of them had rather large MS spikes during the test. I will do more and upload the results to show the inconsistency the network.
1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 7 ms 7 ms 10.131.16.1
3 7 ms 7 ms 7 ms 24.248.104.94
4 9 ms 8 ms 8 ms 70.169.88.6
5 27 ms 19 ms 21 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 18 ms 17 ms 17 ms xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
7 * * * Request timed out.
8 * * * Request timed out.
9 20 ms 20 ms 19 ms ATT [4.68.62.230]
10 19 ms 19 ms 19 ms cr1.dlstx.ip.att.net [12.123.16.86]
11 18 ms 19 ms 24 ms 12.123.249.169
0
0
ChrisL
Former Moderator
•
0
0
cpierce
New Contributor
•
Here are two more traces, each with what seems like a latency spike during different time. You say that the first trace looked normal but there are always two request time outs where I do not believe there should be. It is a little difficult to get a trace that shows what I am trying to explain. Service does not drop completely but it does spike for a brief moment very often. It makes any online gaming near impossible.
1 <1 ms 2 ms <1 ms 192.168.0.1
2 7 ms 7 ms 7 ms 10.131.16.1
3 11 ms 10 ms 9 ms 24.248.104.94
4 789 ms 9 ms 7 ms 70.169.88.6
5 30 ms 37 ms 29 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 18 ms 18 ms 17 ms xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
7 * * * Request timed out.
8 * * * Request timed out.
9 25 ms 22 ms 23 ms ATT [4.68.62.230]
10 24 ms 22 ms 42 ms cr1.dlstx.ip.att.net [12.123.16.86]
11 33 ms 28 ms 30 ms 12.123.249.169
1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 8 ms 7 ms 10.131.16.1
3 11 ms 7 ms 11 ms 24.248.104.94
4 7 ms 8 ms 10 ms 70.169.88.6
5 841 ms 39 ms 45 ms dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]
6 20 ms 26 ms 18 ms xe-5-1-0.edge5.Dallas3.Level3.net [4.59.32.93]
7 * * * Request timed out.
8 * * * Request timed out.
9 23 ms 22 ms 21 ms ATT [4.68.62.230]
10 21 ms 22 ms 21 ms cr1.dlstx.ip.att.net [12.123.16.86]
11 19 ms 18 ms 22 ms 12.123.249.169
0
0
ChrisL
Former Moderator
•
0
0
cpierce
New Contributor
•
I ran the ping test for a little while and here are some of the results.
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=2365ms TTL=64
Reply from 192.168.0.1: bytes=32 time=999ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1692ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time=1080ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
Reply from 192.168.0.1: bytes=32 time<1ms TTL=64
0
0
DerrickW
Valued Contributor
•
0
0
cpierce
New Contributor
•
This is the latest ping test that I ran after I was told to do so. The previous test I was running were against Google's DNS 8.8.8.8. There are no splits at all. My setup is: outlet directly to the modem/router I was provided by COX, then a straight wired connection from the modem/router to my computer.
0
0
DerrickW
Valued Contributor
•
0
0
cpierce
New Contributor
•
Friday, 4/3/20215, would be the best day. I am pretty available all day but earlier would be better. Contact number XXX-XXX-XXXX
0
0
DerrickW
Valued Contributor
•
0
0
shoozter
New Contributor
•
Hi I am having the same exact problem as you, would I be able to contact you via email to hear your response if cox was able to fix your problem, I would really appreciate it. Thanks
0
0
cpierce
New Contributor
•
Sure thing. I also plan on coming to this thread and updating it with as much information as I can to help future people with the same issue.
0
0
shoozter
New Contributor
•
sounds good, will wait for an update then thanks!
0
0