the downstream at a crawl for days? #1Mbps?
this has been happening for days . the speed supposed to be 50mbps but its been at no more than 5mbps on and off for 6 days now .. been resetting the router but this has happened before with my FIRST router .. i took it back too the store they gave me this one didnt last long before this one went too. you people now rise my price and lower your service ? does that make sense ? i talked to a tech online last night. She said if it persist its the router AGAIN. Its NOT my cables i am directly connected to the outside with an RG6. if i dont get help ill go to the store tomorrow. i live in Gainesville FL ..1.2KViews0likes1Comment
WHEN WILL WE SEE IPv6?
This is my residential account which I've had for the past 2.5 years and once in a while I'll review the SB 6141 logs which show the same consistent errors at the end of every dynamic, 24 hour refresh &/or power failure as well. I've resided in several of the states Cox provides service to and must say that the little old Virginia Beach, VA 23451, 23456 areas have seen little in terms of performance boost over the same period. Having a unique business which serves the large retirement community of West Neck Village and the adjacent homes bordering the Signature Golf Corse has given me plenty of insight as to common problems that could be easily fixed with some accurate, personable discussion in advance with residents here. Almost every house hold visited maintains a Cox internet package along with phone and TV packages bundled in an effort to keep customers under some false belief that they might actually be saving money. I really differ in this opinion and for starters, let's consider the "upgrade anything package" with key emphasis on variables that cypher from anything to words like premier and ultimate internet packages throughout. I can't begin to tell you (yes I do have an extensive log book) the number of times I've not only helped introduce a retiree to the web based account access but further investigation revealed that they were using DOCSIS 2.0 modems at best ranging in with old Motorola SB 51_0 and had no idea that the speed they were bottlenecking at 40 to 50Mbps down and maybe 15 up was nowhere near the potential of the advertised Premier, let alone Ultimate band width delivered. The fact is, your customer information pages are far too vague and Cox has but a few markets with Giga Blast or whatever catch jingle advertised. Further, how can a customer be upgraded to the Ultimate Tier and have a tech (on both occasions they claimed their presence stating all is well) not only provision the account but knowingly leave the antiquated DOCSIS 2.0 modems running on the customer’s account? In so far as IPv6 is concerned, is there a date when we can expect to say good bye to the 6 to 4 standard. My business account is running IPv6 so what gives? I've been the go to guy for computer, electronic, gadget, games and emergency services equipment installs since the infancy of this community (my parents also reside here) and more often than not have scratched my head wondering what the h_ll is going on with proper coverage from actual Cox Techs that were not only helpful, but available from 04' through 07' Now, it's hit and miss with subcontractors who might be trained to run RG through a floor plate, terminate with compressed fitting, screw the cable into said hole "cable" power on the modem with hopefully 110 current (yes there once was a 220 incident) dial up support, provision MAC and Serial number (this floors me as a ultimate speed internet package holder with SB5120 modems) connect the Cat 5e to the router and ask or tell, "well mam, your internet is all up to snuff and we also checked, with your permission as to connectivity through you home router and Walla, you are good to go. As I write this, I'm in area code 23451 and it wouldn't matter if I had single or dual band capable DOCSIS 3.0 modems, I still have yet to see 150 Mbps down and not much past 20 up. I had techs out in which they all concur (hint, I was a cable tech who used his Wavetek CLI-1750 religiously) the infrastructure locally is a hybrid of old, new and salvaged equipment dating back to the late 80s’ So then my question on my account page wants me to upgrade my modem from the SB6141 to a SB6183 dual band modem. Should I invest in hopes that I might actually see the holy grail of 150Mbps? You know how frustrating it is as member of Broadband Reports who probably visits the site 2 or 3 times a year and read the Q & A section for Cox HSI customers only to realize their screen clipping of modem stats indicates 200+Mbps on an average in AZ and other markets compared to your customers in Virginia who will never see service levels comparable to actual Cox Employees who, I’m sure take pride in their work. Honestly, it ** and please excuse the slang but no other term fits your service so well. Oh, how could I depart without asking were one of the so many available Wi-Fi hotspots are down here at the ocean front? Of all the areas that could benefit customers who are existing Cox account holders and vacation in Virginia Beach, only to find that there service provider doesn’t have WIFI locally, Not Hot or Spot Regards, Brian R.2.6KViews0likes1CommentRoanoke [VA] Abysmal Speeds during peak hours 5pm through midnight.
Arris SB6190 modem, Windows 7 x64. Ultimate Tier 200/20. Roanoke County - Virginia Signal levels are all good on the modem just half the speed + packet loss/latency in video games during peak hours 5/6pm - 10/12pm after that the speeds return to normal. I can still watch netflix, browse, and do general things at half the speed sometimes lower like 60mb. Playing any sort of video games that require low latency is out of the question. Nothing running in the background like netflix or any other streaming services, etc. Scanned computer for malware/viruses with eset - nothing. Tried direct connect from modem no router in-between same results. 12/29/2015 - 10PM 12/30/2015 Midnight 1/1/2016 - 10PM 1/2/2016 - 2amish ( When the internet speeds go back to normal) 1/2/2016 - 5pm 1/2/2016 - 7PM 10pm 1/2/16 Tracing route to google.com [74.125.224.96] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms [192.168.1.1] 2 33 ms 33 ms 27 ms 10.64.248.1 3 36 ms 30 ms 30 ms 98.172.172.206 4 402 ms 17 ms 34 ms ashbbprj01-ae3.0.rd.as.cox.net [68.1.0.214] 5 100 ms 22 ms 42 ms 68.105.30.118 6 51 ms 15 ms 17 ms 209.85.252.80 7 136 ms 143 ms 137 ms 72.14.236.152 8 177 ms 155 ms 166 ms 72.14.232.71 9 55 ms 65 ms 61 ms 209.85.247.4 10 62 ms 56 ms 59 ms 72.14.238.83 11 91 ms 89 ms 93 ms 216.239.40.8 12 87 ms 89 ms 91 ms 209.85.247.0 13 81 ms 89 ms 91 ms 209.85.250.245 14 86 ms 95 ms 111 ms lax02s19-in-f0.1e100.net [74.125.224.96] Is my node overloaded?9.3KViews0likes16CommentsPremier down/up speed slow
I have inet premier but speed is a lagging 15-30 down and 2-6 up. I have contacted CS and have gone to the Cox store multiple times but no success in getting the speed I'm paying for. I've cycled the modem, did direct connect, i've replaced the coax splitter, taken out the splitter and direct connected the modem to the coax outlet, but speed never increases. I once hit 54 down and that was under the worst conditions, Wi-Fi connect, modem was not cycled for many days, and old splitter was in place. The only thing I have not tried is hooking up the modem to the junction outside my house to avoid any possible noise on my coax lines in my house. I do have Contour Premier and that seems to work just fine when watching indemand 1080i video. I have a Netgear CG3000D-RG modem 3.0. I'll post screen shots of my logs and connections. Please let me know if there are any suggestions or solutions. Thanks in advance for any help, Matt3.1KViews0likes2Comments
Upgraded to internet Premier but seeing weird speeds
Location: Irvine, Ca I recently upgraded to Internet Premier (100mbit down / 10mbit up). I used to have the next lower pkg, internet preferred which is 50/5 (upload actually isn't listed on the site). I have a Surfboard 6190, and i have 24 bonded download channels (max for Cox) and the apparent max 4 uplink. Support over the phone said signal strength was good when they were provisioning the modem. The weirdness is that i'm seeing the advertised speed for the Premier plan for uplink but i'm only seeing the Internet Preferred speed (50mbit) for the downlink (using multiple methods including the speed test on the Cox site, both wired and wireless). It's almost as if the modem wasn't provisioned correctly for the Internet Premier plan. It definitely looks like an artificial limit i'm hitting and it's just more than odd that it's stopping at my previous plan's download speed limit. I was planning on calling support after work today but I read how much back and forth another customer had with a problem that sounds like it might be the same issue as mine and so i was hoping someone here could help or let me know what to tell support so they can verify the modem is getting the correct config for both the downlink and uplink speeds (or whatever else to double check). other guy's post - issue resolved after Cox support apparently fixed something on their end even though initial support showed no issues. http://forums.cox.com/forum_home/internet_forum/f/5/t/8523.aspx1.9KViews0likes2Comments
Intermittent Internet - Started Today 10/25/2015
Starting this morning, Sunday 10/25/15 I have been troubleshooting an intermittent internet problem. As always, I reset the cable modem and routers and it would work on the reboot, but then the become intermittent again. I checked the modem (an Arris SURFboard SBG6782-AC) diagnostics and found that due to T3 and T 4 errors, the modem was resetting. On searching for an explanation it appears that low signal levels or noise could be the problem. T3 ( Ranging Request Retries Exhausted ) Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem’s power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request. T4 ( Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received ) Explanation: The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting the registration process. Typically, this indicates an occasional, temporary loss of service, but if the problem persists, check for possible service outages or maintenance activity on this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request. This is a cut and paste of the report Time Priority Description Sun Oct 25 18:03:36 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:03:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:36 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:04 2015 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:04 2015 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:02:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:01:37 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:01:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:00:37 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 18:00:04 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:59:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:59:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:58:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:58:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:57:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:57:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:56:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:56:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:55:38 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:55:05 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:54:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:54:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:53:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:53:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:52:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:52:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:51:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:51:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:50:39 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:50:06 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:49:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:49:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:48:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:48:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:47:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:47:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:46:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:46:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:45:40 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:45:07 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:08 2015 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:08 2015 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:44:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:43:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:43:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:42:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:42:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:41:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:41:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:40:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:40:08 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:39:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:39:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:38:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:38:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:37:41 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:37:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:36:42 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:36:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:35:42 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:35:09 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:34:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:34:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:33:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:33:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:32:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:32:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:31:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:31:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:30:43 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:30:10 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:29:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:29:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:28:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:28:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:27:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:27:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:11 2015 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:11 2015 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:26:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:25:44 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:25:11 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:24:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:24:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:23:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:23:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:22:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:22:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:21:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:21:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:20:45 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:20:12 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:19:46 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:19:13 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:18:46 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:18:13 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:17:46 2015 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0; Sun Oct 25 17:17:13 2015 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=90:b1:34:fc:0d:bc;CMTS-MAC=00:13:5f:02:d9:48;CM-QOS=1.1;CM-VER=3.0;6.8KViews0likes20CommentsOklahoma 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.3KViews0likes6CommentsEqual 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.1KViews0likes1Comment
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
Premier down/up speed slow
I have inet premier but speed is a lagging 15-30 down and 2-6 up. I have contacted CS and have gone to the Cox store multiple times but no success in getting the speed I'm paying for. I've cycled the modem, did direct connect, i've replaced the coax splitter, taken out the splitter and direct connected the modem to the coax outlet, but speed never increases. I once hit 54 down and that was under the worst conditions, Wi-Fi connect, modem was not cycled for many days, and old splitter was in place. The only thing I have not tried is hooking up the modem to the junction outside my house to avoid any possible noise on my coax lines in my house. I do have Contour Premier and that seems to work just fine when watching indemand 1080i video. I have a Netgear CG3000D-RG modem 3.0. I'll post screen shots of my logs and connections. Please let me know if there are any suggestions or solutions. Thanks in advance for any help, MattInternet 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:
