Uncorrectables on ALL downstream channels. What could be the problem?
I live in Springfield, VA. I have a Netgear CM600 modem and have been receiving uncorrectables of hundreds of thousands and millions in a very limited uptime (< 24 hours). I am having this problem on every channel operating between 649-813MHz. The amount of uncorrectables varies, but is still very high for all of them. Alongside this problem, I have been experiencing network instability and modem crashing about every hour or so. Side note: I have tested a different modem (Arris SB6190) and have gotten the same, if not worse, results. The event log for each modem has showed me a different combination of errors like: -RCS Partial Service -SYNC Configuration Time out -Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out -No Ranging Response received - T3 time-out Cox Technical Support, including the technician who came into my house, said that everything on their side looked good (GREEN). This problem arose after changing my Motorola SURFboard modem to something from this decade (ie. SB6190 and CM600) due to a small UPLOAD SIDE packet loss issue (1-3%) I was having while gaming online. Never any crashing until now. Between the times when these errors occur in the event log, my internet is lightning fast (besides the upload packet loss issue still being present). >These are the values forDOWNSTREAMwith the Netgear CM600 at an uptime of around 90 minutes. <tabindex=-1>Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 3 687000000 Hz 9.1 dBmV 39.2 dB 214828 132675 2 Locked QAM256 1 675000000 Hz 9.3 dBmV 38.5 dB 65347 12412 3 Locked QAM256 2 681000000 Hz 9.6 dBmV 39.3 dB 92489 14832 4 Locked QAM256 4 693000000 Hz 9.3 dBmV 39.3 dB 219991 161237 5 Locked QAM256 5 699000000 Hz 8.8 dBmV 39.1 dB 232634 167674 6 Locked QAM256 6 705000000 Hz 8.5 dBmV 38.9 dB 231551 125552 7 Locked QAM256 7 711000000 Hz 8.4 dBmV 38.8 dB 206782 73208 8 Locked QAM256 8 717000000 Hz 8.1 dBmV 38.6 dB 159890 36191 9 Locked QAM256 17 771000000 Hz 8.7 dBmV 39.1 dB 37129 42243 10 Locked QAM256 18 777000000 Hz 8.8 dBmV 39.1 dB 30994 4741 11 Locked QAM256 19 783000000 Hz 8.9 dBmV 39.2 dB 24894 2178 12 Locked QAM256 20 789000000 Hz 8.4 dBmV 38.9 dB 22073 3062 13 Locked QAM256 21 795000000 Hz 7.9 dBmV 38.7 dB 15069 2258 14 Locked QAM256 22 801000000 Hz 7.5 dBmV 38.4 dB 12652 1561 15 Locked QAM256 23 807000000 Hz 7.2 dBmV 38.3 dB 20874 5991 16 Locked QAM256 24 813000000 Hz 7.8 dBmV 38.6 dB 58248 76267 UPSTREAM: <tabindex=-1>Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 2560 Ksym/sec 17154000 Hz 44.5 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 21984000 Hz 46.0 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 28414000 Hz 47.0 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 34844000 Hz 47.5 dBmV 5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV (I assume that I do not have the option for 8 Upstream channels because the Arris SB6190 did not even list the last 4 channels) Could this problem possibly be inside my home? The technician took out a splitter from my setup and placed my internet cable on a splitter with an amplifier. The problem does not seem to have changed though. I have another, higher-level, technician coming in 2 days. Is there anything that I can show them to help pinpoint the problem?Solved16KViews1like18CommentsCox throttling speeds to gaming servers? I think so.
So I've just had it with Cox and their seemingly dishonest practice of blaming everything on the customer... I just got the 300mbps service in Las Vegas, and suspiciously get 500% increases in ping to gaming services as opposed to standard browsing/streaming service. I've validated everything is good to go on my end, and spent an hour or more being treated like a fool with Cox "technical support" people who don't even know what ping or traceroute are. As a background I've worked in IT for 15+ years and manage large load balanced networks like this for a living... Either there is an immense amount of ineptitude and apathy going on, or they're trying to push gamers to spend more money. My modem is a DOCSIS 3.1 enabled modem. My router is a gigabit router. I'm wired into the router with CAT6 cable, directly. My connection to the COX gateway is fast, and fine. The issue is the Cox internal routing. In this case, I'm going to use League of Legends for an example since they post their server IPs publicly. All I need to do to show where the breakdown is occurring is run a simple tracert. It's clear that I'm getting solid ping to Cox's gateway - langbprj01-ae1.rd.la.cox.net [68.1.1.13] - but they're choosing to route gaming traffic specifically through some kind of WAF, concentrator, or other type of internal network device which is throttling all traffic to 60-70ms (at lowest) The glaring technical evidence: Tracing route to 104.160.131.3 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 8 ms 7 ms 10.67.0.1 3 8 ms 8 ms 7 ms 100.127.4.164 4 11 ms 7 ms 11 ms 100.120.102.24 5 15 ms 16 ms 12 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13] 6 60 ms 61 ms 61 ms 72.215.224.162 <---- the offending Cox IP. 7 61 ms 67 ms 65 ms 104.160.152.223 8 62 ms 61 ms 60 ms 104.160.152.227 9 67 ms 70 ms 70 ms 104.160.159.100 10 68 ms 67 ms 68 ms 104.160.131.3 So why are they throttling gaming speeds to 60-70ms? It doesn't really make sense until you realize they've just started marketing their "Cox Elite Gaming" service to unlock higher speeds for a premium monthly rate. The only problem? I CAN'T EVEN BUY THEIR EXTRA SERVICE IN MY AREA. Come on! If you're going to scam me into buying a premium service, at least offer the option to buy it! My only option has been to reduce my service to the 150mgps service (why bother with bandwidth if it's slow), and subscribe to Haste for a slight ping boost to try and compensate. Note - COX - you're losing money here. In the end I'm just getting screwed, and Cox is showing how dishonest they are. If they could explain exactly what that IP is and why they refuse to address it internally, maybe it will matter. Until then I'll be planning my exit ASAP.9.4KViews1like11CommentsInternet Download Speed Extremely Slow
I just figured out how to add my own account to my mom's. We've been having issues with our speed since we've had Cox. I understand there's too many people on the node (from local tech that came to our house last month), but we weren't told we were going to have problems like this. I can't take a Cox speed test, because only my mother's account can do that. Here's our speeds from November 21-25 of 2015: tests. We are supposed to get "up to 100 Mbps" but here lately we haven't been able to even reach 10 Mbps. To top it off, because of how slow it is if all three of us are online at the same time, we can't do anything. Yes, we're from Northwest Arkansas where it's been raining a lot recently, but we've been having problems before the rain. Lately we've been thinking our problem might be that we're on a splitter with a neighbor, because we've done some looking into it and some people's problems have been that. They ended up getting their own line and they were fine. We have the DPQ3925 gateway and my parents don't have the money to buy our own modem and router. When I get my refund in the spring from financial aid, I've been planning on building a computer, but if the internet is horrible, why build something that I can't enjoy. I just made a League of Legends team and I need to practice daily, but I can't because of the problems we're having. Are you guys able to find out when they're fixing the node in our area? Results from Riot's League of Legends' official network diagnostic: Begin Test! 07:58 PM Sat 01/02/2016 192.64.170.15 Game Servers (ORD1): Tracing route to 192.64.170.15 over a maximum of 20 hops 1 1 ms 7 ms 2 ms 192.168.0.1 2 10 ms 13 ms 13 ms 10.50.128.1 3 10 ms 11 ms 14 ms wsip-70-182-122-10.ks.ks.cox.net [70.182.122.10] 4 10 ms 17 ms 8 ms wsip-70-182-122-46.ks.ks.cox.net [70.182.122.46] 5 * * * Request timed out. 6 23 ms 29 ms 27 ms 70.183.71.84 7 31 ms 30 ms 32 ms chgobprj01-ae0.0.rd.ch.cox.net [68.1.4.42] 8 32 ms 29 ms 30 ms ip70-167-150-114.at.at.cox.net [70.167.150.114] 9 72 ms 29 ms 28 ms 104.160.131.44 10 30 ms 31 ms 30 ms 104.160.131.101 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. Trace complete. 192.64.173.40 Game Servers (ORD1): Tracing route to 192.64.173.40 over a maximum of 20 hops 1 1 ms 1 ms 1 ms 192.168.0.1 2 * * * Request timed out. 3 * * * Request timed out. 4 * * 10 ms wsip-70-182-122-46.ks.ks.cox.net [70.182.122.46] 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 32 ms 30 ms 31 ms ip70-167-150-114.at.at.cox.net [70.167.150.114] 9 42 ms 30 ms 29 ms 104.160.131.46 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. Trace complete. 104.60.131.4 Chiacgo (ORD1): Tracing route to 104.160.131.4 over a maximum of 20 hops 1 4 ms 3 ms 1 ms 192.168.0.1 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * 28 ms 70.183.71.84 7 35 ms 33 ms 33 ms chgobprj01-ae0.0.rd.ch.cox.net [68.1.4.42] 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 30 ms 34 ms 34 ms 104.160.131.4 Trace complete. Google: Pinging 8.8.8.8 with 32 bytes of data: Request timed out. Request timed out. Reply from 8.8.8.8: bytes=32 time=37ms TTL=53 Reply from 8.8.8.8: bytes=32 time=31ms TTL=53 Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 31ms, Maximum = 37ms, Average = 34ms Tracing route to google-public-dns-a.google.com [8.8.8.8] over a maximum of 20 hops: 1 1 ms 1 ms 1 ms 192.168.0.1 2 * * * Request timed out. 3 * * 10 ms wsip-70-182-122-10.ks.ks.cox.net [70.182.122.10] 4 10 ms 12 ms 23 ms wsip-70-182-122-46.ks.ks.cox.net [70.182.122.46] 5 * * * Request timed out. 6 19 ms 21 ms 23 ms 70.183.71.84 7 * 31 ms 32 ms dalsbprj01-ae1.0.rd.dl.cox.net [68.1.2.109] 8 35 ms 31 ms 33 ms 72.14.212.233 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 31 ms 30 ms 42 ms google-public-dns-a.google.com [8.8.8.8] Trace complete. Local Network Info: Windows IP Configuration Host Name . . . . . . . . . . . . : HoodedDemon Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Ethernet: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek PCIe FE Family Controller Physical Address. . . . . . . . . : 00-8C-FA-A9-F5-A9 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Local Area Connection* 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter Physical Address. . . . . . . . . : 66-5A-04-0A-09-3F DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Wireless LAN adapter Wi-Fi: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek RTL8188EE Wireless LAN 802.11n PCI-E NIC Physical Address. . . . . . . . . : 64-5A-04-0A-09-3F DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::104b:e570:b87d:fcd%8(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.11(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Saturday, January 2, 2016 7:56:55 PM Lease Expires . . . . . . . . . . : Saturday, January 2, 2016 8:56:55 PM Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 73685508 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-8B-BC-90-00-8C-FA-A9-F5-A9 DNS Servers . . . . . . . . . . . : 68.105.28.11 68.105.29.11 68.105.28.12 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:2cc0:3ba4:b722:c27a(Preferred) Link-local IPv6 Address . . . . . : fe80::2cc0:3ba4:b722:c27a%4(Preferred) Default Gateway . . . . . . . . . : :: DHCPv6 IAID . . . . . . . . . . . : 335544320 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-8B-BC-90-00-8C-FA-A9-F5-A9 NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{6A43BEC1-5D47-48F6-B56C-9518EF28AD38}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Test Complete! 08:03 PM Sat 01/02/2016Solved7.4KViews0likes19CommentsHigh latency during online gaming.
Hello, As the title says, I have been suffering from severe lag and latency spikes almost constantly when playing online games with Blizzard servers. The time of day doesn't seem to affect it and doing generic router restarts doesn't make a difference. This has been going on for several weeks now and it is becoming unbearable. Any advice on how to fix would be appreciated.5.6KViews1like23CommentsPacket loss SW Las Vegas
Hello, I am having serve packetloss that affects my ability to play online games. I get about 20 seconds of normal play and then drop packets for about 5-10 seconds. I have tried all the standard trouble shooting such as rebooting both modem and router, removing router from network and just having computer connected, making sure I have good cat6 cables etc. I have an Arris Surfboard SB8200 DOCSIS 3.1 Cable Modem and NETGEAR Orbi Home Mesh WiFi System (RBK50) Below are some trace routes. Previously I have had only one or two days of this kind of issue a month but now for the last 5 days straight I am dropping so many packets that I cannot play any online games as it is not enjoyable for any game that requires some reaction time and even a turn based game like hearthstone is frustrating as I cannot play cards while the packets are dropping. I just want to know if there is an issue in my area. Tracing route to www.google.com [172.217.14.68] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * 5 ms 5 ms 10.89.0.1 3 7 ms 8 ms 7 ms 100.127.5.132 4 7 ms 7 ms 7 ms 100.120.102.36 5 58 ms 25 ms 56 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13] 6 13 ms 13 ms 13 ms 72.215.224.173 7 * * * Request timed out. 8 15 ms 14 ms 14 ms 66.249.94.216 9 13 ms 13 ms 13 ms 108.170.247.147 10 14 ms 13 ms 13 ms 108.170.234.15 11 15 ms 12 ms 13 ms 108.170.230.120 12 13 ms 14 ms 13 ms 108.170.247.225 13 15 ms 13 ms 14 ms 74.125.251.39 14 15 ms 12 ms 13 ms lax17s38-in-f4.1e100.net [172.217.14.68] Trace complete. C:\Users\bostaurus> C:\Users\bostaurus> C:\Users\bostaurus> C:\Users\bostaurus> C:\Users\bostaurus>tracert cox.com Tracing route to cox.com [45.60.45.167] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 7 ms 6 ms 8 ms 10.89.0.1 3 7 ms 8 ms 7 ms 100.127.5.134 4 13 ms 22 ms 22 ms 100.120.102.40 5 13 ms 12 ms 9 ms ae56.bar1.LasVegas1.Level3.net [4.35.34.213] 6 * * * Request timed out. 7 13 ms 13 ms 13 ms 4.7.26.34 8 13 ms 13 ms 15 ms 45.60.45.167 Trace complete. C:\Users\bostaurus>tracert google.com Tracing route to google.com [172.217.11.174] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 9 ms 7 ms 8 ms 10.89.0.1 3 * 8 ms 7 ms 100.127.5.132 4 14 ms 12 ms 6 ms 100.120.102.36 5 * 13 ms 12 ms langbprj01-ae1.rd.la.cox.net [68.1.1.13] 6 25 ms 13 ms 12 ms 72.215.224.173 7 * * * Request timed out. 8 13 ms 23 ms 13 ms 108.170.234.212 9 * 12 ms 12 ms 108.170.225.75 10 * 1211 ms 13 ms lax28s15-in-f14.1e100.net [172.217.11.174] Trace complete. C:\Users\bostaurus>5.5KViews0likes1CommentPacket loss, latency on gigablast in Scottsdale, AZ for the last few months
I've been battling issues similar to multiple other recent posts on the forums [1, 2, 3, 4].Since this problem has started, I've replaced the cabling in my house, gotten a new modem and a new router, but the problem has persisted. As of today, I've had four different techs come to my house. Techs 1 and 2 both replaced the connections from my house to my tap. Tech 3 did that too, but also said he added a "boost filter" because of "low transmits" to my modem. Tech 4 replaced connections as well, and then said he "lowered the signal" because it was "too high" at the modem (sounds like he removed the boost filter from tech #3 lol). Today I noticed there is one especially bad host in the tracerts to both a sample Rocket League server and to Google, and several other hosts giving packet loss. Sunday and Monday had very bad packet loss all day, while it cleared late Monday night (9pm-1am). Today there was supposedly an outage in my area, but my Internet access was fine, and in fact had very little packet loss. Lo and behold, as the "outage" was clearing up, the packet loss came back. Attached are several samples from yesterday and today. I chose a smattering of times from yesterday's samples to show that the problem was definitely exacerbated during peak times, but that there is still packet loss in the tracert on Cox's end even outside of peak, which persists even after today's supposed outage was fixed. In addition to this, the last phone tech I spoke to via the Cox Cares (what a BS name) actually remarked that Arizona was the highest reporter of these issues in their personal experience. To me, that's pretty telling. Obviously it's anecdotal, but with my data and the rest of the data from others it seems to me Cox has some serious infrastructure issues that they are actively choosing to avoid dealing with. Lucky for them they have a monopoly here, huh? https://drive.google.com/file/d/1irw5zdTEkkEb5818-UJJBkbLkP6DHzFM/view?usp=sharing https://drive.google.com/file/d/1pkmfPBba58rBVsLE1dvU53BGUTjvKtNN/view?usp=sharing https://drive.google.com/file/d/1gHbb7vwUXIT2FXpFvoeNbbpUsogvPwT7/view?usp=sharing https://drive.google.com/file/d/1RmCGIvrtx1Sc1Q7w0yU7b6gbJP_ggy3G/view?usp=sharing https://drive.google.com/file/d/1TmK8voj4KXR4li6N7XahocB4uA6HC5m1/view?usp=sharing https://drive.google.com/file/d/1bLOWFfg9vnDwZ6PAbCz1G_406JJmSeXe/view?usp=sharing https://drive.google.com/file/d/1LhWZxlJoREkhb7Fji6HAZ0X6EIC6J55d/view?usp=sharing https://drive.google.com/file/d/19YF_sdIIG8sAyVAQorc_fYIj0X6cjlHO/view?usp=sharing [1]Gaming and warzone/CoD in general packet burst - Internet - Internet Forum - Cox Support Forums [2]Noisy node issues - Speed drops until reset - Internet - Internet Forum - Cox Support Forums [3]Terrible packet loss and jitter. - Internet - Internet Forum - Cox Support Forums [4]Another packet loss and ping spike issue - Internet - Internet Forum - Cox Support Forums5.4KViews1like25CommentsWarcraft disconnect issues the minute I subscribed to COX in Henderson, NV
I have been a Cox customer for about 2 weeks (since moving to Henderson). Since then, World of Warcraft is unplayable for me. I cannot go 15 consecutive minutes without a disconnect or a lag spike of more than 5-15 seconds. Is anyone else having problems with WoW? It's not my computer--WoW still works perfectly fine with no issues when I drive back to Glendale, CA and use my brother's ISP, nor does it have disconnect or lag issues using my Mom's old DSL connection. It's only here in Henderson, using Cox. For example (and this is not an extreme case, but about the average experience for me): This evening, Tuesday August 13, from 9:00 pm-9:40 pm, I disconnected 4 times from WoW. I also had 4 bouts of lag/latency that had me running in place onscreen for more than 10 seconds each time. And it doesn't matter what time of day I try to play. Morning, mid-day, evenings, weekdays or weekends, it's all the same. I am a "Preferred" bundle customer, which is up to 25mbps download speeds. Should I pay extra and upgrade to 50 mbps? I wouldn't mind doing so, but the product I'm paying for now is so horrendous, I don't trust that paying extra would solve anything. Especially since my old DSL connection never had any problems like the ones I've experienced since the cable guy installed my internet and router and I plugged in two weeks ago. Everything else I do online, I can do from my smartphone--so if I can't play online, then there really is no reason to keep paying for Cox internet.Solved5.4KViews0likes5CommentsGaming and warzone/CoD in general packet burst
I've done everything I could. Replaced the modem, gotten a separate router with SQM/QoS capabilities, called a tech out, there have been no answers. I pay $120 on my bill every month for 500mbs and nothing to show for it. It's the most frustrating thing to have around 30-50ms ping but still have lag stutters, packet burst symbol pop up, and faulty hit registration due to speed spikes. Who else is feeling this? I want to back to 150, but its even worst! Can't even play a game due to the heavy lag. Is there a fix? Cause everyone at cox seems to be dismissive and gives no real answers or solutions.5.3KViews1like4Comments20%+ packet loss for hours sporadically throughout the day (unusable)
Hello, At the beginning of the month (the 3rd), I moved into a brand new apartment complex that is fiber ready. They also installed a brand new Cox modem. I figured that this meant I wouldn't have any issues. I was very wrong. Since moving in, I have made many calls to Cox support and even had 2 techs out (a 3rd scheduled for tomorrow) and nothing has improved whatsoever. I work from home and I also do a lot of online gaming and this packet loss makes everything impossible to do (including loading websites). I have tried everything on my end that I can do, including power cycling the modem, rebooting my computer, changing the ethernet cables, turned off Wireless, turned off Firewalls. The two previous techs replaced the wiring outside hoping that will fix it, but nothing has worked. The packet loss I'm experiencing is making my TCP connections completely unusable, while my UDP connections still work somewhat. My computer is plugged directly into the modem. When the internet is working, it's great and downloads very fast, but when it's having issues, it spikes to upwards of 35-40% packet loss. The issue usually occurs from around 2AM-8AM, but the issue often happens sporadically throughout the day (as you can see from my Pingplotter of the last 48 hours below...) and thus far, no tech has been able to see the problem happening live. I'm beyond frustrated at this point and I just don't know what to do anymore. Any help would be appreciated. I've provided various tests below that might offer some insight into the issues.4.8KViews0likes9CommentsGaming Lag
Hello, i am having a problem in which every time I connect to a game of League of Legends it lags to an unplayable level. Once I connect, if I then power cycle my modem it fixes it for the most part (some packet loss but okay). I know it is not the game servers as I was in CO for the past two months and never had this issue. In March I was having a similar issue and when I called Cox said not their fault, get a new modem/router. I did and problem was actually fixed until I went to CO in May. Once I returned, same issue. Issue increases dramatically at 5pm. Pretty sure that cox is throttling the service to Riot servers. All other services I.e Netflix, YouTube work fine.4.6KViews0likes10Comments