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
Our community is a collaborative place to learn about Cox products and services. Jump into the conversation today!
New Contributor
•
4 Messages
Closed
I am getting severe, intermittent packet loss while I play online games.
It seems to only happen when I interact with other players, usually 4 or more at a time. When I play solo in these games, even though I am still connected, I do not usually notice anything out of the ordinary.
For some specifics:
When I play Dota 2, one of out of every 3 or 4 times I encounter an enemy player results in packet loss. I try to move my character, but the game does not respond. I can still see everyone else around me moving, but my actions do not register until it is usually too late. Yesterday this happened to me so I ran a "-ping" command in game as quickly as I could. I caught the tail end of the spike and it showed 798 ping with 14% packet loss. I checked about 5 seconds later and it was back to around 60 ping with 0% packet loss. These spikes last anywhere from 2-5 or 6 seconds.
In WoW, the same type of thing happens, except everything freezes. My actions don't register, but everything around me freezes as well. My ping during those times (from the game client) show ~800-1300ms.
I have experienced this same thing in CS:GO, Destiny on my PS4, Arma 3, Borderlands 2, and pretty much any game I can play online among others. But as I said, I only see issues when I am around those other players.
I have called Cox support and the tier 2 tech said he saw some issues with my connection, so a tech was sent out. The tech basically told me that it's a cabling issue, but since I live in an apartment complex, we can't do much about it because we would have to rewire a quarter mile of cables.
I have run a few tracert's to Valve's server that I play on most, located in Seattle.
Z:\Users\Kyle>tracert eat.valve.net
Tracing route to eat.valve.net [192.69.96.1]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 6 ms 7 ms 7 ms 10.36.72.1
3 8 ms 7 ms 7 ms 172.21.2.138
4 31 ms 22 ms 27 ms 70.169.73.196
5 20 ms 19 ms 19 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13]
6 20 ms 21 ms 20 ms 68.105.30.150
7 * * * Request timed out.
8 21 ms 21 ms 20 ms ae0.cr2.lax112.us.zip.zayo.com [64.125.32.78]
9 29 ms 29 ms 32 ms ae1.cr2.sjc2.us.zip.zayo.com [64.125.31.233]
10 46 ms 46 ms 45 ms v22.ae29.mpr2.sea1.us.zip.zayo.com [64.125.31.38
]
11 47 ms 47 ms 51 ms 128.177.117.130.IPYX-094067-002-ZYO.zip.zayo.com
[128.177.117.130]
12 * * * Request timed out.
13 52 ms 51 ms 52 ms eat.valve.net [192.69.96.1]
Trace complete.
I also ping'd that same server for a bit. Here is a shortened version of the results with the most important parts in it.
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=66ms TTL=56
Reply from 192.69.96.1: bytes=32 time=60ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=2003ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=59ms TTL=56
Reply from 192.69.96.1: bytes=32 time=66ms TTL=56
Reply from 192.69.96.1: bytes=32 time=78ms TTL=56
Reply from 192.69.96.1: bytes=32 time=54ms TTL=56
Reply from 192.69.96.1: bytes=32 time=63ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=54ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=68ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=59ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=69ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=60ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=70ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=59ms TTL=56
Reply from 192.69.96.1: bytes=32 time=950ms TTL=56
Reply from 192.69.96.1: bytes=32 time=51ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=53ms TTL=56
Reply from 192.69.96.1: bytes=32 time=52ms TTL=56
Ping statistics for 192.69.96.1:
Packets: Sent = 86, Received = 86, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 51ms, Maximum = 2003ms, Average = 87ms
I am not sure what exactly is happening overall. I am willing to accept that it may indeed be my apartment complex's wiring, or even my own hardware. But I would like to get to the bottom of this if we can.
Discussions
•
Updated
4.8K
6
0
0
Pro Connect Charges
Discussions
1
0
Internet outage 24 hrs
Discussions
4
0
Billing cycle
Discussions
1
0
Bills
Discussions
1
0
Pro Connect Charges
Discussions
1
0
Billing cycle
Discussions
1
0
Package site
Discussions
1
0
Bills
Discussions
1
0
Internet outage 24 hrs
Discussions
4
0
kjasperse
New Contributor
•
I forgot to mention, I am wired in on my PC as well as my PS4, no WiFi is used except on mobile devices.
As far as peak hours, I do not believe this is happening solely in those hours, as I was playing Dota some time after 10 PM
0
0
ChrisL
Former Moderator
•
0
0
kjasperse
New Contributor
•
I ping'd them both at the same time, and did see a jump at the same moment
My ping to the server jumped to 920ms, and my ping to the gateway jumped to 566ms.
Does this mean it's my end? ie. cabling or hardware?
0
0
DerrickW
Valued Contributor
•
0
0
kjasperse
New Contributor
•
I believe it was reset when I spoke to support over the phone, but not since then. That was maybe two months ago.
And yes, wired connection the whole time
0
0
DerrickW
Valued Contributor
•
0
0