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?Solved16KViews1like18Comments
Only 3 of 4 upstream channels bonded in DOCSIS 3. Is this normal?
My DOCSIS 3.0 cable modem's status page says: Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 3 5120 Ksym/sec 36100000 Hz 43.5 dBmV 2 Locked TDMA and ATDMA 1 2560 Ksym/sec 23300000 Hz 39.0 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 29600000 Hz 41.0 dBmV 4 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV Is it normal that only 3 of the 4 upstream channels are bonded? I am using the same coaxial cable for internet as for my satellite dish with an in-line amplifier and attenuator on the modem. Does this limit my bandwidth and make it so that my upstream channel 4 doesn't lock? thanks14KViews0likes8Comments
Constant Upload Problems in Rogers AR
I'm posting here because I'm tired of trying to explain this to Cox Support over the phone. It will be pretty long so please bare with me. This is going on in south Rogers, AR. For the last 3 to 4 weeks I've been noticing issues with the bonded upstream channels, causing my internet connection to time out and occasionally cause the modem to reset automatically. Currently I have 3 upload channels (channels 2, 3 and 4), and out of the 3, channels 3 and 4 are constantly timing out, showing an "Aborted" status within the modem's diagnostics (192.168.100.1). Sometime after Cox does some repairs (assuming somewhere in their distribution), it seems to happen again. It also happens some hours after I have reset the modem via Cox automated and live person calls. It gets worse on the weekends. Now, this is my history with Cox Support: - Some weeks ago, when I called Cox some time after I started noticing the issues, I found out that this area was flagged for an outage. So I waited a day to call again. It seemed to go back to normal for a few days then it started again. - By the second time I called, the support person said that the outage was taken care of and they sent in the tech to check my connection. The tech showed up, very good tech by the way, and proceeded to replace all of my coax connections and splitters (I already have RG6 cable throughout my house). He ran his tests checking for noises and he couldn't see anything wrong within my house. The power levels in the modem improved, so I can testify of the great signals I still have at this point (I work with electronics). After checking all this, he stated that if the problem persisted, that it would most likely be outage related, which I agree 100%. It worked great for a few of days. - This last week it started yet again to drop the 2 channels so I went to buy a new modem to see if it would help. I upgraded from the SB6121 to the SB6141 to get the 8 channels of downstream. I must say, that the internet was working fine before I installed the new modem so I expected it to work after the installation. It worked good for a couple of days until yesterday (10/18/2013). My modem did automatic resets several times. I also did a full factory default reset, just like I've dome some times before in case it helped. I would have internet for less than 1 hour before it would time out again. - So when I called yesterday (10/18/2013), I spoke to support and they stated that my area was flagged for an outage and that someone was out troubleshooting. So I waited until today to check it out. After some time using on the internet, I noticed that it dropped the channels again. My modem has not automatically reset yet. - Here is the info I'm seeing from my modem Please note that the Dowstream channels are working perfectly at 37-38dB Signal to Noise Ratio and 0dBmV Power Levels ------------- Upstream Channels --------------------- Upstream Bonding Channel Value Channel ID 3 2 4 Frequency 28700000 Hz 23700000 Hz 35300000 Hz Ranging Service ID 4250 4250 4250 Symbol Rate 5.120 Msym/sec 2.560 Msym/sec 5.120 Msym/sec Power Level 41 dBmV 41 dBmV 44 dBmV Upstream Modulation [ 6 ] 16QAM [ 6 ] 16QAM [ 6 ] 16QAM Ranging Status Aborted Success Aborted ----------------------- Log Posts ------------------------------ Once the channels go to Aborted status, the log FILLS COMPLETELY with messages like this: Time Priority Code Message Oct 19 2013 18:02:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:cf;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:15 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:14 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:14 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:13 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:13 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:12 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:12 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:11 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; Oct 19 2013 15:32:11 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0; ------------------------------------------------------------------ With all this said, is there someone in these forums that can help with this issue? Concluding from what the tech said and my opinion, the problem is not within my household, it seems to be withing the Cox infrastructure. I would appreciate it if someone forwards this message to a person that would have good understanding of this situation and could perhaps give an update on what is going on. Thank you!!Solved5.1KViews0likes7CommentsUpstream packet loss and jitter
We're experiencing latency spikes and packet loss throughout the day. It appears to be upstream based on testing I've done so far. All the details are below. It comes and goes suddenly and seemingly at random, and does tend to fade away during the night as if it were congestion. Had a tech come out, he just left. Said he checked the line all the way from the modem to the tap and the signals were all excellent. Once he reconnected the service I could immediately see high jitter and packet loss in PingPlotter. He said there's not much we can do since the signals are all good. We have the Panoramic WiFi Gateway. The modem was originally bridged, but I factory reset it in an attempt to debug this issue -- didn't help. Jitter and packet loss is seen simultaneously by two desktops wired directly into the modem (well, through a wall). I recently saw the modem reboot itself on its own when the issue was happening. Not sure if related. I've been running PingPlotter for a few days against the following targets: Google DNS (8.8.8.8) CloudFlare DNS (1.1.1.1) The default gateway assigned to my modem (resolves to ipxx-xxx-xx-x.ph.ph.cox.net) The modem itself (192.168.1.1) The jitter spikes and packet loss occur simultaneously in all of these targets except for the modem itself which remains stable.I will attach plenty of screenshots at the end of this post. When analyzing results from Google or CloudFlare in PingPlotter, I see the same thing many others on these forums have seen: The first hop is the modem (192.168.1.1) with no issues. The second hop is a private IP that is likely the CMTS (10.97.32.1). Continuous packet loss always begins here. The default gateway (that IP which resolves to ipxx-xxx-xx-x.ph.ph.cox.net) shows the same packet loss but does not have any intermediary hops like the CMTS. I've also been running basic tests with packetlosstest.com and have beenable to reliably correlate those results to the packet loss shown in PingPlotter. According to packetlosstest.com the loss is only upstream. I've performed dozens of tests and I have only ever seen upstream packet loss. During the worst times I've had speed tests shownearly 0.1 Mbps upload. The download was also poor, but speedtest.netuses TCP so that's not necessarily an issue. See screenshot further below. This can get extremely disruptive of any online activities that require stability, especially VoIP and live screen sharing. Iusually have totether my phone and useexpensive LTE to do some of these tasks. If it can be looked into or ifwe can get any advice on how to proceed, we would highly appreciate it! Now for some screenshots... PingPlotter 24hSummary: Please ignore the red block towards the end, that was the technician doing his work. You can see the 24 hour pattern here. It seems to follow a congestion pattern, though I've also experienced thisissue as late as 2-3am several times (haven't caught it that late on PingPlotter yet). PingPlotter to CloudFlare: Just an example showing continuous PL starting at the famous second hop (CMTS) for a regular web connection. It's the same exact story across all target websites. Packet Loss Test: This is one of many examples of packetlosstest.com showing upstream packet loss. The activity on the right from PingPlotter occurred during the test and correlates with the packet loss seen in the test. The order of targets in PingPlotter are different and there's more, but the top timeline graph is still the modem and the rest include the same targets as above. PingPlotter (while I was typing up this post): I was going to look for a time to zoom in on where it goes from decent to bad very suddenly, and I didn't need to look for one as it started happening right then and there. If I was on a voice call, sharing my screen, or playing an online game right now, I'd be having a very rough time. I ran packetlosstest.com shortly after but ithad calmed down by then, still showed 1.7% though. Speed Test: I got lucky with this one since the packet loss comes and goes very quickly and it's hard to capture in some tests without blowing 20 minutes doing them repeatedly.It slowed down this speed test to such an extent that my 300/30 Mbps connection became this. The next speed test was a lot better. This was on Feb 20 long before I began monitoring with PingPlotter. I will try to reproduce in the future and correlate with PingPlotter. Modem upstream: The tech said all the signals were excellent so I'm not really concerned with it being an issue on my end. Downstream signals have been steady all this time with SNRalways at least35 dB and usually in the 40-41 range. Power levels have also been good, well within -5 and 5 dBmV. Here's upstream: There are "uncorrectable codewords" on the modem, but these only appeared after the technician came and disconnected service for his testing. Before that, there were 0 uncorrectables. I'm not sure if that could have caused them, so I'll include this image just in case.3.6KViews0likes7Comments
Oklahoma City / Edmond - Upload Power Levels Unstable - Causing T3 Timeout / Outages
I am near 14140 Broadway Ext, in Edmond, OK. I believe we are having a partial service interruption going on 3 days. I have humored tech support up to and including re-flashing my firmware on my modem. I can't rule out being a traffic increase relation, i.e. the neighbors are home in the evening, but the issues were prevalent all day Friday. Event Logs: Sat Oct 10 07:21:37 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 04:59:36 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 02:51:26 2015 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 00:35:43 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Sat Oct 10 00:35:28 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:29:08 2015 Warning (5) Dynamic Range Window violation Fri Oct 09 22:28:33 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:28:09 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 21:39:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 21:38:49 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 14:52:12 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 14:51:29 2015 Notice (6) TLV-11 - unrecognized OID;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.0;CM-VER=3.0; Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+ DOCSIS Network Access Enabled Allowed Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked QAM256 50 819000000 Hz -0.1 dBmV 38.4 dB 305 574 2 Locked QAM256 49 813000000 Hz 0.0 dBmV 38.5 dB 427 699 3 Locked QAM256 51 825000000 Hz 0.3 dBmV 38.6 dB 238 512 4 Locked QAM256 52 831000000 Hz 0.5 dBmV 38.9 dB 151 443 5 Locked QAM256 53 837000000 Hz 0.1 dBmV 38.9 dB 159 157 6 Locked QAM256 54 843000000 Hz -1.4 dBmV 38.3 dB 140 106 7 Locked QAM256 55 849000000 Hz -1.6 dBmV 38.3 dB 194 293 8 Locked QAM256 56 855000000 Hz -2.0 dBmV 38.2 dB 274 417 9 Locked QAM256 57 861000000 Hz -2.5 dBmV 38.3 dB 255 531 10 Locked QAM256 58 867000000 Hz -2.9 dBmV 38.3 dB 452 638 11 Locked QAM256 59 873000000 Hz -2.4 dBmV 38.3 dB 415 568 12 Locked QAM256 60 879000000 Hz -2.8 dBmV 38.1 dB 223 433 13 Locked QAM256 61 885000000 Hz -3.0 dBmV 38.1 dB 172 415 14 Locked QAM256 62 891000000 Hz -3.0 dBmV 38.2 dB 106 182 15 Locked QAM256 63 897000000 Hz -2.7 dBmV 38.3 dB 121 130 16 Locked QAM256 64 903000000 Hz -4.1 dBmV 37.8 dB 42417 51328 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 2560 Ksym/sec 22600000 Hz 47.0 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 27500000 Hz 47.0 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 34000000 Hz 48.0 dBmV 4 Locked ATDMA 4 2560 Ksym/sec 38900000 Hz 47.5 dBmV Tech support was useless today though, they can't escalate till a technician has been on site. Funnily enough the technician has been on site 2 times now. This latest issues though has been on going issue for at least 3 days. Help Desk Ticket Reference: #2942900 Checked with my neighbors, two are experiencing it, a third didn't report any issues and I found three other forum posts, exhibiting the same or similar behavior in my area. Atypical error seen in logs: Started Unicast Maintenance Ranging - No Response received - T3 time-out; My Steps to Reproduce: Saturate your upload bandwidth 100% for 1 to 2 minutes consistently. Time out occurs, the modem may go offline, but the connection is definitely lost. Power levels at the time of upload are approaching 52.0+. It's definitely something new on Cox's end as this has only been an issue for about 72 hours. Any form of upload saturation disconnects the modem, so all connectivity is interrupted. A house full of Netflix users is not a big deal, but the minute I upload something to a FTP or play Destiny utilizing P2P hosting, the whole internet goes offline. I have some time stamps of occurrence, I set my computer to test upload in 5 minute intervals using the newer/unbiased speed test website: http://www.testmy.net Speedtest.net is not really seeing any issue so I looked for alternatives. Packet loss is 0%, unless a T3 time out is just about to occur then we start seeing it go up in %. That's expected since a timeout is in progress. The correlation is that just before disconnection, upload speeds / bandwidths are low. Examples: Fri Oct 09 2015 @ 10:26:16 pm - Upload Speed - 4.59 Mb/s (avg is normally 11.5 Mb/s) Fri Oct 09 22:29:08 2015 Warning (5) Dynamic Range Window violation Fri Oct 09 22:28:33 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Fri Oct 09 22:28:09 2015 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=6c:ca:08:72:9c:f1;CMTS-MAC=00:19:2f:e6:7f:b2;CM-QOS=1.1;CM-VER=3.0; Further Details: Motorola SB6183, 16xDown, 4xUp, Firmware Version: SB6183-9.2.0.0-GA-04-37-NOSH Firmware reflashed, multiple restarts/resets, removed the router from the equation, checked all fittings, last service visit "replaced" some fittings, not sure what else, they didn't communicate to my wife what they had done. They were here visiting, despite Cox finally admitting to a local outage.3.3KViews0likes6Comments
Internet Issues
I recently got a modem upgrade to a Cisco DPQ3212, and I've been experiencing a slow internet connection since it got activated for about a month now. I'm not really sure what is the optimal level for the Downstream/Upstream Channels, but it looks off to me. With Splitter: With Splitter off:2.5KViews0likes3Comments
Increasing frequency T3 intermittent timeouts
I've been having t3 interference and subsequent intermittent disconnects for about a year now, have had techs out multiple times only to tell me they dont know the reason its happening. Linked is pics of what I think is the issue -- upstream bonded noise, I have changed modems 3 times (all self-produced), currently these stats are with Netgear CG3000Dv2 , its happening more and more often, I'm about to cancel service if I can't solve the problem. =( (I dc'd twice while writing this.)2.2KViews0likes4CommentsEqual upload speed
Just wondering why cox does not offer equal download and upload speeds. Would the price be crazy? currently I have the prefered internet package and its 50mbps download and only 5mbps upload. Ultimate and Premiere offer 25mbps upload but why only that much? and why such a difference from the prefered package would be a bit nicer to pay for 50mbps download and at least 10mbps upload. Anybody else agree with me???2.1KViews0likes1CommentWhy can't Cox Fix My Internet
Ever since I moved into this house years ago, I have had intermittent connection issues. Multiple service reps have been out here to "diagnose" my connection, but no one can ever seem to pinpoint the cause of my connection. I have recently cut everything but internet (because we know Cox is a monopoly in this service), and I continue to have connection issues. It's only the UPLOAD I have issues with. I pay for: 100 Mbps DOWN, 10 Mbps UP. My last test I received: 86.33 Mbps DOWN, 0.00 UP, with a 44% packet loss (29 ms latency, which is acceptable). It has always beenan issue with my UPSTREAM connection. Multiple modems being used, no change. When performing this test, I always disconnect from the router and connect straight into the modem so we can ensure the router is not causing the issue. I have used Cox's provided routers with the same issue, but currently I am using a retail router. I am so tired of paying so much money to get so little back. I would just like to get a working internet connection Edit: I would like to mention this issue is sporadic. Sometimes it works, sometimes it doesn't. I can run a test with a normal range then come back in 5 minutes and I get the above. 20 minutes later it may work againif I am lucky, but if it does, then I can expect it to go down within another 10-20 minutes. No consistency, which is what makes diagnosing my issue such a problem.1.7KViews0likes2Comments
Dropping Upstream Channels
I am having trouble with my modem losing upstream channels. It seems to only happen when it is hot outside and primarily between around 11:00 am and 6:00 pm. I tried contacting technical support and while the person I talked to was courteous, he was not listening to what I was telling him. He said I needed a firmware update, so he pushed one out to my modem. Problem is the so called firmware update matches exactly the one from the screen shot I took two days before. Update, not so much. Imagine my surprise when that did not fix the issue. Is there anyone here that can help? my modem is aCisco DPC3010 DOCSIS 3.0.1.4KViews0likes1Comment
Internet Issues
I recently got a modem upgrade to a Cisco DPQ3212, and I've been experiencing a slow internet connection since it got activated for about a month now. I'm not really sure what is the optimal level for the Downstream/Upstream Channels, but it looks off to me. With Splitter: With Splitter off:Why can't Cox Fix My Internet
Ever since I moved into this house years ago, I have had intermittent connection issues. Multiple service reps have been out here to "diagnose" my connection, but no one can ever seem to pinpoint the cause of my connection. I have recently cut everything but internet (because we know Cox is a monopoly in this service), and I continue to have connection issues. It's only the UPLOAD I have issues with. I pay for: 100 Mbps DOWN, 10 Mbps UP. My last test I received: 86.33 Mbps DOWN, 0.00 UP, with a 44% packet loss (29 ms latency, which is acceptable). It has always beenan issue with my UPSTREAM connection. Multiple modems being used, no change. When performing this test, I always disconnect from the router and connect straight into the modem so we can ensure the router is not causing the issue. I have used Cox's provided routers with the same issue, but currently I am using a retail router. I am so tired of paying so much money to get so little back. I would just like to get a working internet connection Edit: I would like to mention this issue is sporadic. Sometimes it works, sometimes it doesn't. I can run a test with a normal range then come back in 5 minutes and I get the above. 20 minutes later it may work againif I am lucky, but if it does, then I can expect it to go down within another 10-20 minutes. No consistency, which is what makes diagnosing my issue such a problem.
