Very high ping spikes to the second hop, 10.xxx.

Any tracert I run goes through the same ip, which as a 10.xxx so should be part of Cox's private network:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 10 ms 60 ms 10.33.40.1

Pinging it yields alarming results:

Pinging 10.33.40.1 with 32 bytes of data:
Reply from 10.33.40.1: bytes=32 time=14ms TTL=254
Reply from 10.33.40.1: bytes=32 time=14ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=19ms TTL=254
Reply from 10.33.40.1: bytes=32 time=10ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=12ms TTL=254
Reply from 10.33.40.1: bytes=32 time=27ms TTL=254
Reply from 10.33.40.1: bytes=32 time=13ms TTL=254
Reply from 10.33.40.1: bytes=32 time=27ms TTL=254
Reply from 10.33.40.1: bytes=32 time=19ms TTL=254
Reply from 10.33.40.1: bytes=32 time=87ms TTL=254
Reply from 10.33.40.1: bytes=32 time=35ms TTL=254
Reply from 10.33.40.1: bytes=32 time=123ms TTL=254
Reply from 10.33.40.1: bytes=32 time=77ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=49ms TTL=254
Reply from 10.33.40.1: bytes=32 time=16ms TTL=254
Reply from 10.33.40.1: bytes=32 time=12ms TTL=254
Reply from 10.33.40.1: bytes=32 time=13ms TTL=254
Reply from 10.33.40.1: bytes=32 time=17ms TTL=254
Reply from 10.33.40.1: bytes=32 time=45ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=105ms TTL=254
Reply from 10.33.40.1: bytes=32 time=26ms TTL=254
Reply from 10.33.40.1: bytes=32 time=30ms TTL=254
Reply from 10.33.40.1: bytes=32 time=110ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=14ms TTL=254
Reply from 10.33.40.1: bytes=32 time=75ms TTL=254
Reply from 10.33.40.1: bytes=32 time=35ms TTL=254
Reply from 10.33.40.1: bytes=32 time=147ms TTL=254
Reply from 10.33.40.1: bytes=32 time=23ms TTL=254
Reply from 10.33.40.1: bytes=32 time=70ms TTL=254
Reply from 10.33.40.1: bytes=32 time=124ms TTL=254
Request timed out.
Reply from 10.33.40.1: bytes=32 time=42ms TTL=254
Reply from 10.33.40.1: bytes=32 time=36ms TTL=254
Reply from 10.33.40.1: bytes=32 time=63ms TTL=254
Reply from 10.33.40.1: bytes=32 time=55ms TTL=254
Reply from 10.33.40.1: bytes=32 time=41ms TTL=254
Reply from 10.33.40.1: bytes=32 time=114ms TTL=254
Reply from 10.33.40.1: bytes=32 time=113ms TTL=254
Reply from 10.33.40.1: bytes=32 time=43ms TTL=254
Reply from 10.33.40.1: bytes=32 time=18ms TTL=254
Reply from 10.33.40.1: bytes=32 time=29ms TTL=254
Reply from 10.33.40.1: bytes=32 time=50ms TTL=254
Reply from 10.33.40.1: bytes=32 time=17ms TTL=254
Reply from 10.33.40.1: bytes=32 time=45ms TTL=254
Reply from 10.33.40.1: bytes=32 time=11ms TTL=254
Reply from 10.33.40.1: bytes=32 time=38ms TTL=254
Reply from 10.33.40.1: bytes=32 time=45ms TTL=254
Reply from 10.33.40.1: bytes=32 time=42ms TTL=254
Reply from 10.33.40.1: bytes=32 time=13ms TTL=254
Reply from 10.33.40.1: bytes=32 time=66ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=41ms TTL=254
Reply from 10.33.40.1: bytes=32 time=48ms TTL=254
Reply from 10.33.40.1: bytes=32 time=37ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=10ms TTL=254
Reply from 10.33.40.1: bytes=32 time=57ms TTL=254
Reply from 10.33.40.1: bytes=32 time=28ms TTL=254
Reply from 10.33.40.1: bytes=32 time=28ms TTL=254
Reply from 10.33.40.1: bytes=32 time=63ms TTL=254
Reply from 10.33.40.1: bytes=32 time=59ms TTL=254
Reply from 10.33.40.1: bytes=32 time=47ms TTL=254
Reply from 10.33.40.1: bytes=32 time=31ms TTL=254
Reply from 10.33.40.1: bytes=32 time=22ms TTL=254
Reply from 10.33.40.1: bytes=32 time=11ms TTL=254
Reply from 10.33.40.1: bytes=32 time=27ms TTL=254
Reply from 10.33.40.1: bytes=32 time=13ms TTL=254
Reply from 10.33.40.1: bytes=32 time=12ms TTL=254
Reply from 10.33.40.1: bytes=32 time=31ms TTL=254
Reply from 10.33.40.1: bytes=32 time=11ms TTL=254
Reply from 10.33.40.1: bytes=32 time=12ms TTL=254
Reply from 10.33.40.1: bytes=32 time=12ms TTL=254
Reply from 10.33.40.1: bytes=32 time=16ms TTL=254
Reply from 10.33.40.1: bytes=32 time=43ms TTL=254
Reply from 10.33.40.1: bytes=32 time=49ms TTL=254
Reply from 10.33.40.1: bytes=32 time=12ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=10ms TTL=254
Reply from 10.33.40.1: bytes=32 time=41ms TTL=254
Reply from 10.33.40.1: bytes=32 time=43ms TTL=254
Reply from 10.33.40.1: bytes=32 time=23ms TTL=254
Reply from 10.33.40.1: bytes=32 time=15ms TTL=254
Reply from 10.33.40.1: bytes=32 time=73ms TTL=254
Reply from 10.33.40.1: bytes=32 time=14ms TTL=254
Reply from 10.33.40.1: bytes=32 time=43ms TTL=254
Reply from 10.33.40.1: bytes=32 time=33ms TTL=254
Reply from 10.33.40.1: bytes=32 time=16ms TTL=254
Reply from 10.33.40.1: bytes=32 time=26ms TTL=254
Reply from 10.33.40.1: bytes=32 time=12ms TTL=254
Reply from 10.33.40.1: bytes=32 time=10ms TTL=254
Reply from 10.33.40.1: bytes=32 time=60ms TTL=254
Reply from 10.33.40.1: bytes=32 time=39ms TTL=254
Reply from 10.33.40.1: bytes=32 time=19ms TTL=254
Reply from 10.33.40.1: bytes=32 time=25ms TTL=254
Reply from 10.33.40.1: bytes=32 time=17ms TTL=254

Ping statistics for 10.33.40.1:
Packets: Sent = 100, Received = 99, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 147ms, Average = 36ms

I am plugged directly into the router, and there's nothing using any significant bandwidth on my local network.

Any idea what this server is? Even if it's in Phoenix, and even in the best case scenario, 14 ms is a bit high, but I'm getting nasty ping spikes which show up everywhere else. What should I do? Please help.

Responses

MrObvious15

New Contributor II

•

4 Messages

5 years ago

Sounds like bufferbloat from an overwhelmed interface on their end. If you can get through I'd have Cox look further.

0

0

BVE

New Contributor

•

1 Message

5 years ago

I'm in the same boat as you are. There is a bad node somewhere. I just got done speaking with them and they gave me the standard answer of they can only troubleshoot from the street to the modem. Unacceptable!! I know what I'm talking about. The issue for me started about 3 weeks ago. The Latency is horrible.

2

0

KleeWai

New Contributor III

•

25 Messages

BVE, you are absolutely correct and we all are in the same boat. These stupid problems hits hard, especially for us gamers. Most cox customer support staff are unaware and don't really know whats going on and are just doing what the higher-ups tell them to do. On this forum - https://forums.cox.com/forum_home/internet_forum/f/internet-forum/25474/finally-admitting-they-screwed-up some guy was able to squeeze the right information out of a technician. https://drive.google.com/file/d/12VKXPFY6ff9JkgCzCcmhBKIRFsP77JmX/view The best thing we all can do right now is to file an FCC complaint like some people are saying and asking your neighbours who have Cox to file one too.

Like

Reply

5 years ago

DannyS

Moderator

•

588 Messages

Hello, if still having these concerns and have already performed the basic testing such as reboots, directly wired testing and confirming on multiple devices. Please reach us on Twitter at @CoxHelp, visit us on Facebook, or email at cox.help@cox.com. Provide us your name and the complete service address with a link to this thread so we can get started.

Like

Reply

5 years ago

0

DannyS

Moderator

•

588 Messages

5 years ago

Hello, if you are still having concerns regarding your service? Please reach us on Twitter at @CoxHelp, visit us on Facebook, or email at cox.help@cox.com. Provide us your name and the complete service address with a link to this thread so we can get started.

0

0

Axsdenied

New Contributor

•

1 Message

5 years ago

I'm having this same issue and have been logging 24 hours a day. I wrote a script to only log latency events above 30 ms, which is generous for the first hop of the network. In a 24 hour period I've logged 14,000 events.

I've had the guys out to the house to check from the pole to the house (checks out fine). They checked from the pole to the node (checked out fine).

I ran a histogram chart, based on time blocks, to see if there are any trends and sure enough there is. Between 12:30am and 6:30 am are minimal events, below 10. After that it sky rockets. This suggests MAJOR congestion (Cox says it's Covid19 induced). To be clear my total bandwidth on my gigablast is acceptable (usually from 700 to 900 Mbps), it's just the latency that is terrible.

Its affecting my online game playing at my video conference calls. Long story short, they can't fix the issue until life normalizes.

2

0

KleeWai

New Contributor III

•

25 Messages

feelsbadman, PLEASE DO SOMETHING COX

Like

Reply

5 years ago

0

APWOCALA

New Contributor

•

2 Messages

This has been the case for me for over a year.

Like

Reply

5 years ago

0

arrowyourboat

New Contributor

•

1 Message

5 years ago

Same.

0

0

Zurq

Contributor II

•

270 Messages

5 years ago

same boat, bad packetloss in pretty much anything, VOIP, Games, etc

0

0