Upstream Packet Loss/Jitter causing issues gaming.

Question

So over the last few months Ive been noticing strange issues while gaming relating to my network. According to the in-game network monitor Im getting packet loss on the upstream side, typically 1-5% loss with small spikes of up to 15% when its steadily happening and occasionally Ill have 20-30 seconds of 25%+ loss measured on the upstream. I checked all of my own equipment which was replaced within the last 6months to a year due to a lightning strike travelling up my coax and frying every piece of hardware attached to it including the motherboard to my computer.
Started my diagnostics from there, checked my modem downstream/upstream power levels and snr, was well within spec according to the manufacturer website. (Arris Surfboard SB6183, doesnt have the ** intel puma chipset). Ran a tracert to servers of multiple games I play and began working backwards till I found a hard dropout at the second hop leaving my apartment, 100.122.126.114. Numbers like these were consistent, the crazy ping spikes for a second hop, but this was the only single lost packet. The games Im playing are sending over 100p/s so Im assuming the issue is more pronounced. Pinging like this is a measly 1/s.Reply from 100.122.126.114: bytes=256 time=9ms TTL=254Reply from 100.122.126.114: bytes=256 time=4ms TTL=254Reply from 100.122.126.114: bytes=256 time=4ms TTL=254Reply from 100.122.126.114: bytes=256 time=7ms TTL=254Reply from 100.122.126.114: bytes=256 time=7ms TTL=254Reply from 100.122.126.114: bytes=256 time=9ms TTL=254Reply from 100.122.126.114: bytes=256 time=24ms TTL=254Reply from 100.122.126.114: bytes=256 time=23ms TTL=254Reply from 100.122.126.114: bytes=256 time=20ms TTL=254Reply from 100.122.126.114: bytes=256 time=36ms TTL=254Reply from 100.122.126.114: bytes=256 time=28ms TTL=254Reply from 100.122.126.114: bytes=256 time=47ms TTL=254Reply from 100.122.126.114: bytes=256 time=31ms TTL=254Reply from 100.122.126.114: bytes=256 time=32ms TTL=254Reply from 100.122.126.114: bytes=256 time=31ms TTL=254Request timed out.Reply from 100.122.126.114: bytes=256 time=34ms TTL=254Reply from 100.122.126.114: bytes=256 time=35ms TTL=254Reply from 100.122.126.114: bytes=256 time=32ms TTL=254Reply from 100.122.126.114: bytes=256 time=35ms TTL=254Reply from 100.122.126.114: bytes=256 time=29ms TTL=254Reply from 100.122.126.114: bytes=256 time=29ms TTL=254Reply from 100.122.126.114: bytes=256 time=26ms TTL=254Reply from 100.122.126.114: bytes=256 time=35ms TTL=254Reply from 100.122.126.114: bytes=256 time=8ms TTL=254Reply from 100.122.126.114: bytes=256 time=9ms TTL=254Reply from 100.122.126.114: bytes=256 time=7ms TTL=254Reply from 100.122.126.114: bytes=256 time=9ms TTL=254Reply from 100.122.126.114: bytes=256 time=8ms TTL=254Reply from 100.122.126.114: bytes=256 time=9ms TTL=254Reply from 100.122.126.114: bytes=256 time=8ms TTL=254
Began running the same test to the first hop, 10.132.32.1. And while I didnt have an dropped packets, I feel like this jitter is whats causing my in-game network monitor to shout out packet loss because UDP and jitter don't get along well.Reply from 10.132.32.1: bytes=256 time=9ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=11ms TTL=254Reply from 10.132.32.1: bytes=256 time=9ms TTL=254Reply from 10.132.32.1: bytes=256 time=23ms TTL=254Reply from 10.132.32.1: bytes=256 time=15ms TTL=254Reply from 10.132.32.1: bytes=256 time=9ms TTL=254Reply from 10.132.32.1: bytes=256 time=9ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=10ms TTL=254Reply from 10.132.32.1: bytes=256 time=39ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=12ms TTL=254Reply from 10.132.32.1: bytes=256 time=13ms TTL=254Reply from 10.132.32.1: bytes=256 time=22ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=14ms TTL=254Reply from 10.132.32.1: bytes=256 time=14ms TTL=254Reply from 10.132.32.1: bytes=256 time=10ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=22ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=10ms TTL=254Reply from 10.132.32.1: bytes=256 time=18ms TTL=254Reply from 10.132.32.1: bytes=256 time=6ms TTL=254Reply from 10.132.32.1: bytes=256 time=11ms TTL=254Reply from 10.132.32.1: bytes=256 time=10ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=8ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=7ms TTL=254Reply from 10.132.32.1: bytes=256 time=14ms TTL=254Reply from 10.132.32.1: bytes=256 time=6ms TTL=254Reply from 10.132.32.1: bytes=256 time=6ms TTL=254
Tech came out 5/6/19 and replaced the coax end at the wall outlet and at the other end at a box outside my apartment somewhere. Was told if the issue arose again to contact customer support and request a bucket truck to check the nodes. I noticed it wasnt even fixed before he made it out to his truck. Called again, another tech came out 5/8/19, tested the line with the diagnostic tool, told me there was nothing wrong. Was told he was checking the outside lines. Came back with a picture on his phone of the diagnostic tool showing me everything was good. I have no way of knowing if the picture was even legitimate.&nbsp;

becky · Answer

Hi Xearu, your modem metrics look excellent, and I'm unable to detect any packet loss. Please let us know the result of the service call scheduled for this afternoon. -Becky, Cox Support Forums Moderator

morgan1982 · Answer

Its cox, dont you know they are terrible for gaming. But hey for $15 more a month you can get elite gamer package to help them be the first company to take advantage of customers after the lift of net neutrality. Happy gaming!!

Forum Discussion

Upstream Packet Loss/Jitter causing issues gaming.

Related Content

Upstream packet loss and jitter

Upstream packet loss and jitter

Intermittent internet quality and upstream issues

What causes T3 timeouts?

intermittent cable modem resets caused by signal drop

Recent Discussions

Internet Consistently goes down everyday

How do I give good feedback?

E-mail

Need a new cord

1 month free!....