High ping - Tracert question

Hi — I’m seeing frequent latency spikes when playing a game. I ran tracert to 8.8.8.8 from my PC and got this:

1 5 ms 1 ms 1 ms 192.168.0.1
2 13 ms 107 ms 93 ms 10.36.80.1
3 20 ms 12 ms 109 ms 100.127.74.74
4 16 ms 81 ms 13 ms 100.120.100.16
5 83 ms 104 ms 94 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 87 ms 93 ms 78 ms ip72-215-224-173.pn.at.cox.net [72.215.224.173]
7 107 ms 99 ms 99 ms 142.251.238.107
8 66 ms 105 ms 92 ms 209.85.249.95
9 40 ms 100 ms 102 ms dns.google [8.8.8.8]

Is this an issue in the Cox network (hop 2–6)? How to get this issue resolved?

Already tried restarting my gateway which did not fix the issue.

Responses

Accepted Solution

M

Mouse0

Visitor

•

4 Messages

The issue is resolved now by using a WiFi adapter.

0

DustinP

Moderator

•

1.1K Messages

Hello Mouse0,

There doesn't appear to be an obvious sign of an issue from this tracert. Are issues only apparent while on a particular game? If multiple devices are facing an impact, is the issue present during a particular time of day or is it random throughout the day? If we're looking at the time the issue is present, then we may get an idea of how to approach helpful troubleshooting steps. You should not have to keep rebooting the Gateway. We can take a look to see if there is any obvious sign of an issue when you have a moment to email us at Cox.Help@cox.com with your name, complete address, and include the URL to your forum comment.

-Dustin

2

0

Darkatt

Honored Contributor

•

2K Messages

@DustinP There are no problems. Routers are programmed to respond to regular traffic with a higher priority than a ping/tracert. Your tracert actually looks good. Remember 100ms, is 1/10th a second, and since ping isn't a high priority, those numbers actually look fairly decent.

Also, are you doing your tracert/ping over ethernet or wifi? WiFi is going to be slower.

(edited)

Like

Reply

0

M

Mouse0

Visitor

•

4 Messages

@Darkatt

There was very frequent ping spikes. And I seen that on ethernet it is normal.

But the issue is resolved now by using a WiFi adapter.

(edited)

Like

Reply

0

M

Mouse0

Visitor

•

4 Messages

Thank you for your reply. I will send the email as you requested.

The ping is too high overall. It can fluctuate quite a bit.

For example here is a ping I did on 8.8.8.8 (Google). In this example it was mostly ~25ms at first and then shot up quite a bit.

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=86ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=24ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=24ms TTL=251
Reply from 8.8.8.8: bytes=32 time=69ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=24ms TTL=251
Reply from 8.8.8.8: bytes=32 time=26ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=24ms TTL=251
Reply from 8.8.8.8: bytes=32 time=24ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=27ms TTL=251
Reply from 8.8.8.8: bytes=32 time=23ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=23ms TTL=251
Reply from 8.8.8.8: bytes=32 time=26ms TTL=251
Reply from 8.8.8.8: bytes=32 time=24ms TTL=251
Reply from 8.8.8.8: bytes=32 time=26ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Request timed out.
Reply from 8.8.8.8: bytes=32 time=96ms TTL=251
Reply from 8.8.8.8: bytes=32 time=104ms TTL=251
Reply from 8.8.8.8: bytes=32 time=112ms TTL=251
Reply from 8.8.8.8: bytes=32 time=25ms TTL=251
Reply from 8.8.8.8: bytes=32 time=129ms TTL=251
Reply from 8.8.8.8: bytes=32 time=38ms TTL=251
Reply from 8.8.8.8: bytes=32 time=44ms TTL=251
Reply from 8.8.8.8: bytes=32 time=53ms TTL=251
Reply from 8.8.8.8: bytes=32 time=62ms TTL=251
Reply from 8.8.8.8: bytes=32 time=70ms TTL=251
Reply from 8.8.8.8: bytes=32 time=78ms TTL=251
Reply from 8.8.8.8: bytes=32 time=87ms TTL=251
Reply from 8.8.8.8: bytes=32 time=101ms TTL=251
Reply from 8.8.8.8: bytes=32 time=105ms TTL=251
Reply from 8.8.8.8: bytes=32 time=113ms TTL=251
Reply from 8.8.8.8: bytes=32 time=121ms TTL=251
Reply from 8.8.8.8: bytes=32 time=217ms TTL=251
Reply from 8.8.8.8: bytes=32 time=21ms TTL=251
Reply from 8.8.8.8: bytes=32 time=27ms TTL=251
Reply from 8.8.8.8: bytes=32 time=143ms TTL=251
Reply from 8.8.8.8: bytes=32 time=45ms TTL=251
Reply from 8.8.8.8: bytes=32 time=57ms TTL=251
Reply from 8.8.8.8: bytes=32 time=65ms TTL=251
Reply from 8.8.8.8: bytes=32 time=73ms TTL=251
Reply from 8.8.8.8: bytes=32 time=81ms TTL=251
Reply from 8.8.8.8: bytes=32 time=89ms TTL=251
Reply from 8.8.8.8: bytes=32 time=97ms TTL=251
Reply from 8.8.8.8: bytes=32 time=105ms TTL=251
Reply from 8.8.8.8: bytes=32 time=26ms TTL=251
Reply from 8.8.8.8: bytes=32 time=121ms TTL=251
Reply from 8.8.8.8: bytes=32 time=133ms TTL=251
Reply from 8.8.8.8: bytes=32 time=38ms TTL=251
Reply from 8.8.8.8: bytes=32 time=24ms TTL=251
Reply from 8.8.8.8: bytes=32 time=55ms TTL=251
Reply from 8.8.8.8: bytes=32 time=63ms TTL=251
Reply from 8.8.8.8: bytes=32 time=73ms TTL=251
Reply from 8.8.8.8: bytes=32 time=79ms TTL=251
Reply from 8.8.8.8: bytes=32 time=87ms TTL=251
Reply from 8.8.8.8: bytes=32 time=106ms TTL=251
Reply from 8.8.8.8: bytes=32 time=104ms TTL=251
Reply from 8.8.8.8: bytes=32 time=113ms TTL=251

(edited)

0

Welcome to the Cox Community

High ping - Tracert question

Darkatt

Mouse0

Related Content

Recent Discussions