Ping & Packet loss [Megathread]
Collecting the threads where people are saying they have ping and packet loss issues. Unlikely that this wide spread problem is caused by a "router", "signal issue" or "bent cables" (unless somehow everyone's cables got bent over night across the country? Santa Claus?) These problems are ranging from California to New Orleans, Arizona and Nevada between. I know these are unusual times but also sending technicians to check cables or trying to blame modems, house cabling for the issues doesn't help. What can you do: Install PingPlotter (14day trial) and start collecting data. 1.1.1.1 and 8.8.8.8 are Google's anycast DNS servers that should be optimized for latency. You could also try to ping cox.net, zoom.us, google.com or try to find your game server addresses. Try to collect several days of data to see how the service degrades in certain peak times Post the results here and email cox.help@cox.com with the data and your issues/location etc.See if you get an answer or anything helpful to address. In some cases they want to send technician over but if you already had technician check your signals or cables, it's likely not going to help If the problem persist, consider filing informal FCC complaint as azchips didon his case Cox, what can you do: Escalate these issues to your manager/director customer support who can then escalate it further, hopefully up to the CEO/whoever is the director of Cox Communication. Acknowledge that the issues exists and communicate to customers what is happening, what you plan to do and when. Email customers affected or post in this forums or on twitter. Launch your own investigation to the network look for bottlenecks, speed up your upgrade plans if you can. Even after this crisis, we are likely to see increase in businesses and consumers internet usage. Focus improving the latency in the overall network. This is what most people are complaining about it. Since affects how fast new connections open, dns requests get resolved, and providing good experience for applications that require stable and constant connectivity (video calls, ssh, gaming). Threads (most of these are from the last couple of weeks): I'm getting really tired of this. (Ping spikes and packet loss) Ping Spikes and Jitter Tired of Latency and Packet Loss High Jitter causing instability in voice programs along with games. High Packet Loss and High Max ping to first hop after cable modem - Mesa, AZ, Gigablast How many people on your Node? High ping and packet loss on Gigablast (San Diego) NV - Intermittent latency spikes and packet loss, mostly in the evening Extreme packet loss while gaming/voip (San Diego, CA) Abysmal Internet Random Ping Spikes and Packet Loss Excessively High Ping, Jitter, Intermittent packet loss, connection almost useless between 6-11pm Congestion and slowness during Community Peak, Cox blames modem, tries to rent new one. Ping spikes in North Las Vegas area Severe packet loss Tucson - Packetloss / jitter Packet loss/High latency Packet Loss, Gaming, VOIP problems Lag issues with Specific Server High Pings and Jitters along with Packet Loss High Latency, Packet Loss, and Slow Speeds Fortnite Packetloss High latency, terrible speeds. Packet Loss occuring many in evening times in New Orleans East area New Issue of the day with Continued Packet Loss and High Latency Horrible Intermittent Lag Spikes when online gaming High latency during online gaming. Packet loss/bad connection Rocket League Extreme Lag on Cox Panoramic - Wired Connection Packet loss for a month now.15KViews10likes12Comments
Arris SB6190 Cable Modem - RCS Partial Service and SYNC Time Sync Failure (100% Packet Loss)
I've gone through 3 cable modems, 3 wireless routers, and a handful of ethernet cables thinking it was a problem with my hardware. I've blocked every other device on the network for troubleshooting this. It's just my PC on it, hardwired in. The internet works without issues for about 90-120seconds at a time, then there's a 30 second period where I get 100% packet loss on everything. I can't get on any websites, I get disconnected from any games I'm running, etc. Then after 30 seconds, everything reconnects okay. I've rebooted all of my devices three times. I've called Cox and they said everything is testing fine. There's no Cox maintenance in the area and no outages. No construction in the vicinity.Is there anything I could do to diagnose this? Can I buy anything to test the coax drop in the wall or something? https://www.docdroid.net/tJH6C5a/event-log.pdf.htmlscreenshots of the Event Log from the modem page https://www.docdroid.net/RFmVJY2/status.pdf.htmlscreenshots of the Status page but I don't know what any of this means12KViews0likes11Comments
Lag spikes every minute or so, please help!
Since I've gotten my new router lag spikes started popping out of no where, they are VERY frequent and are very annoying, especially while playing online games. Here's a test for my ping I did a couple of minutes ago. Pinging google.com [74.125.224.34] with 32 bytes of d Reply from 74.125.224.34: bytes=32 time=109ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=46ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=170ms TTL=55 Reply from 74.125.224.34: bytes=32 time=133ms TTL=55 Reply from 74.125.224.34: bytes=32 time=33ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=37ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=39ms TTL=55 Reply from 74.125.224.34: bytes=32 time=43ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=61ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=34ms TTL=55 Reply from 74.125.224.34: bytes=32 time=34ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=108ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=37ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=33ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=35ms TTL=55 Reply from 74.125.224.34: bytes=32 time=33ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=34ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=37ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=33ms TTL=55 Reply from 74.125.224.34: bytes=32 time=29ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=31ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=30ms TTL=55 Reply from 74.125.224.34: bytes=32 time=32ms TTL=55 Reply from 74.125.224.34: bytes=32 time=33ms TTL=55 Here is another test. Pinging google.com [74.125.224.110] with 32 bytes of Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=106ms TTL=55 Reply from 74.125.224.110: bytes=32 time=32ms TTL=55 Reply from 74.125.224.110: bytes=32 time=46ms TTL=55 Reply from 74.125.224.110: bytes=32 time=66ms TTL=55 Reply from 74.125.224.110: bytes=32 time=89ms TTL=55 Reply from 74.125.224.110: bytes=32 time=111ms TTL=55 Reply from 74.125.224.110: bytes=32 time=36ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=35ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=40ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=35ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=35ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=109ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=34ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=34ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=37ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=32ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=26ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=148ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=37ms TTL=55 Reply from 74.125.224.110: bytes=32 time=58ms TTL=55 Reply from 74.125.224.110: bytes=32 time=80ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=34ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=29ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 Reply from 74.125.224.110: bytes=32 time=31ms TTL=55 Reply from 74.125.224.110: bytes=32 time=30ms TTL=55 Reply from 74.125.224.110: bytes=32 time=32ms TTL=55 Reply from 74.125.224.110: bytes=32 time=28ms TTL=55 The highest was around a 100, which to me, a 100 is VERY acceptable, I used to have a 100 ping before and it was normal, but the lag I'm getting in games do not feel like a 100, more like a thousand. Please help, I've tried restarting my modem but that did not work. I've also had this going on for about a week.8.8KViews0likes22Comments
Experiencing Lag during online gaming
Hi, I'm experiencing lag and stutter during online gaming. I've Cox Preferred plan and play game over wireless connection. I've tried restarting and rebooting modem several times but the issue still remains. I also tried playing game using the LAN connection but the issue persists. I've contacted customer support twice but they have only helped me by restarting the connection again and again. For debugging purposes, I ran Speedtests (www.speedtest.net) and Pingtests (www.pingtest.net), and i figured out speed fluctuations, at times I get 63.2 Mbps and other time I get 12.2 Mbps. Also, I get 9ms, 12ms and other time 223ms and 300+ pings. These figures are from tests that I ran back to back when I started facing issues during gameplay. Please look into this issue. I've Netgear C3700DOCSIS 3.0 cable modem router and I'm using 2.4 GHz connection for wireless connection. Thanks, Gaurav K.7.9KViews0likes12Comments
Problem with traffic to Blizzard servers (World of Warcraft) via Cogentco
http://forums.cox.com/forum_home/internet_forum/f/5/t/1146.aspx Here is a link to a thread about an issue that occurred in January where many players were experiencing high latency on World of Warcraft servers mainly due to the Cogentco connection between Cox and AT&T. The issue disappeared awhile ago and now it is happening again where I am getting 100-300 MS on servers where I would usually be at around 20 MS. I'm not sure what was fixed last time in order to solve this problem but I would like some feedback on this issue. I would say the issue started about 3-4 days ago and based on this forum post: http://us.battle.net/wow/en/forum/topic/9793019207 many other Cox Digital Cable users in AZ are experiencing similar issues with high ping due to the Cogentco routing.6.1KViews0likes8Comments
Packet loss from Tustin1.Level3.net plz open a ticket with level3
I have new service from COX and my speed is otherwise fine, but when I log into World of Warcraft I will have 91 lat [good], 76ms [my connection to them Good] 2253ms [VERY BAD, data loss] I looked on a few forums and they suggested a Tracer, the results suggest packet loss from level3.net, this is not a COX node, so the only thing I can do is request that COX puts in a request to level3.net and have them fix their node. Tracing route to 12.129.209.68 over a maximum of 30 hops 0 ******-** [192.168.0.2] 1 192.168.0.1 2 10.104.0.1 3 24-234-16-208.ptp.lvcm.net [24.234.16.208] 4 24-234-6-68.ptp.lvcm.net [24.234.6.68] 5 ae54.bar2.LasVegas1.Level3.net [205.129.18.109] 6 ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 7 ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 8 192.205.37.145 9 cr2.la2ca.ip.att.net [12.122.129.106] 10 12.123.249.73 11 * * * Computing statistics for 250 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 ******-** [192.168.0.2] 0/ 100 = 0% | 1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1 0/ 100 = 0% | 2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.104.0.1 0/ 100 = 0% | 3 7ms 0/ 100 = 0% 0/ 100 = 0% 24-234-16-208.ptp.lvcm.net [24.234.16.208] 0/ 100 = 0% | 4 8ms 0/ 100 = 0% 0/ 100 = 0% 24-234-6-68.ptp.lvcm.net [24.234.6.68] 0/ 100 = 0% | 5 11ms 0/ 100 = 0% 0/ 100 = 0% ae54.bar2.LasVegas1.Level3.net [205.129.18.109] 0/ 100 = 0% | 6 106ms1/ 100 = 1%1/ 100= 1% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 0/ 100 = 0% | 7 107ms1/ 100 = 1%1/ 100= 1% ae-105-3505.bar2.Tustin1.Level3.net [4.69.158.98] 0/ 100 = 0% | 8 107ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.145 100/ 100 =100% | 9 ---100/ 100 =100%0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.129.106] 0/ 100 = 0% | 10 ---100/ 100 =100%0/ 100 = 0% 12.123.249.73 _______________________________________________________ Tracer for pathping 199.108.62.157 > c:\pathping.txt 5 10ms 0/ 100 = 0% 0/ 100 = 0% ae54.bar2.LasVegas1.Level3.net [205.129.18.109] 0/ 100 = 0% | 6 108ms 1/ 100 = 1% 1/ 100 = 1% ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102] 0/ 100 = 0% | 7 106ms 0/ 100 = 0% 0/ 100 = 0% ae-106-3506.bar2.Tustin1.Level3.net [4.69.158.102] 3/ 100 = 3% | 8 108ms 3/ 100 = 3% 0/ 100 = 0% 192.205.37.145 97/ 100 = 97% |4KViews0likes3CommentsHorrible Ping Spikes (Tried many solutions)
tl;dr is at the bottom ---------------------------------------------------------------------------------------------------------------------- For awhile now I've been experiencing very small spikes in pretty much all games I play. I'm using a wired connection to my PC. As for what kind of internet I have, it is Gigablast from Cox. I've attempted to use their support multiple times, but on there end it seems like there are no issues so I'm kind of at a lost. I recently got a new router too, going from a Netgear Nighthawk to Cox's Panoramic Gateway. Valorant, CSGO, and Rocket League are the ones I have the biggest problems with. I've updated all of my drivers (network, graphics, and chipset), bios, and windows hoping for some sort of fix but to no avail. Resetting my modem/router does nothing, its on the latest firmware, and I've tried multiple channels for my Wi-Fi (I know it doesn't really change my wired connection's perfomance but im desperate) If you're experienced with Valorant, I use both the text and graphics display for system performance. I can see very miniscule packet loss spikes that go all the way up to 100%, but it only lasts for fractions of a second. In CSGO and Rocket League, their network performance displays do not detect any problems. CSGO claims that my performance is fine, with consistent +300 fps, pretty stable ping, and 0% loss in netgraph_1 , but while playing I can see pretty big stutters every couple minutes. I use Command Prompt on the side, and consistently ping 8.8.8.8 (as recommended on the searches I did), I can see spikes that go upwards from 100ms, where as it usually sits roughly around 20ms. Very occasionally the requests even time out. Flushing/renewing my DNS and different ethernet cables dont work. Im completely at a loss. My friends said turning setting MoCA on might fix it, but the setting doesnt enable for whatever reason. ------------------------------------------------------------------------------------------------------------------------- TL;DR - I get many small spikes in packet loss and ping on my wired connection. Updating windows, bios, and all drivers didn't fix it. Got a new router 2 months ago but the problem still persists. Cox reports back as there are no issues in my network. If anyone has any idea as to what is happening or a potential fix, I'm all ears. Here as some of the results from multiple ping tests https://imgur.com/wf95sn2 https://imgur.com/uKe4prI https://imgur.com/f5M3p9q https://imgur.com/yjNzj6o3.3KViews0likes3CommentsPing spikes
When playing video games like league of legends with my roommate on a 25/mbs connections every 10 minutes we get spikes that go through the roof sometimes up to 4000ms, It's been a real hassle lately and i would like to get it fixed. everytime I have called cox about this problem i get a person that doesnt tell me anything besides the signal looks good, yes but that doesn't fix the problem that my ping spikes randomly high at random times. i've reset the modem got a new router, opened up more channels, etc, nothing works and its not just me and my roommate that has the problem, when we have company over their ping does the same. so if i could please get some help and fix this problem that'd be awesome3.3KViews0likes1Comment
