Internet outages wreaks havoc on VPN connections
This is a follow-up post as it seems my original post is locked for updates. I often loose my connection which only lasts for several minutes up to an hour or so. I am working from home using VPN and a couple minute outage will result in the VPN terminating. I opened a ticket with COX and they replaced my coax running from the house to the the tap outside and stated they also replaced a component in the tap. However, I still experience outages. I am posting my modem logs in hopes that someone can review and provide a recommendation as to the root of the problem? Thanks Status The statuses listed show the connection state of the cable modem. They are used by your service provider to evaluate the operation of the cable modem. Top of Form 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 256QAM 29 903.00 MHz -2.80 dBmV 37.36 dB 385069 1794108 2 Locked 256QAM 9 783.00 MHz -0.50 dBmV 37.64 dB 146898 44701 3 Locked 256QAM 10 789.00 MHz -0.90 dBmV 37.36 dB 147052 41571 4 Locked 256QAM 11 795.00 MHz -1.40 dBmV 37.36 dB 145868 39576 5 Locked 256QAM 12 801.00 MHz -2.60 dBmV 37.64 dB 146245 37172 6 Locked 256QAM 13 807.00 MHz -3.80 dBmV 37.36 dB 143888 29705 7 Locked 256QAM 14 813.00 MHz -3.70 dBmV 37.36 dB 140054 26351 8 Locked 256QAM 15 819.00 MHz -4.00 dBmV 37.36 dB 136900 24781 9 Locked 256QAM 16 825.00 MHz -4.70 dBmV 36.39 dB 133912 23104 10 Locked 256QAM 17 831.00 MHz -4.60 dBmV 36.61 dB 131146 21034 11 Locked 256QAM 18 837.00 MHz -3.80 dBmV 37.36 dB 124720 18624 12 Locked 256QAM 19 843.00 MHz -3.90 dBmV 37.64 dB 121785 16964 13 Locked 256QAM 20 849.00 MHz -4.70 dBmV 36.61 dB 118409 16159 14 Locked 256QAM 21 855.00 MHz -3.80 dBmV 37.36 dB 113816 15485 15 Locked 256QAM 22 861.00 MHz -3.60 dBmV 37.36 dB 111314 14057 16 Locked 256QAM 23 867.00 MHz -4.40 dBmV 36.61 dB 106349 13993 17 Locked 256QAM 24 873.00 MHz -4.60 dBmV 36.39 dB 112914 71318 18 Locked 256QAM 25 879.00 MHz -4.10 dBmV 36.61 dB 178590 342506 19 Locked 256QAM 26 885.00 MHz -4.00 dBmV 36.61 dB 516537 2095976 20 Locked 256QAM 27 891.00 MHz -4.30 dBmV 36.39 dB 126750 122243 21 Locked 256QAM 28 897.00 MHz -3.40 dBmV 37.64 dB 93058 18920 22 Locked 256QAM 30 909.00 MHz -3.20 dBmV 37.36 dB 590716 3136217 23 Locked 256QAM 31 915.00 MHz -2.60 dBmV 37.36 dB 1095897 5620291 24 Locked 256QAM 32 921.00 MHz -2.00 dBmV 38.61 dB 2889497 17273329 25 Locked 256QAM 33 927.00 MHz -2.30 dBmV 37.90 dB 108056 482915 26 Locked 256QAM 34 933.00 MHz -2.30 dBmV 37.60 dB 76276 25344 27 Locked 256QAM 35 939.00 MHz -1.90 dBmV 37.60 dB 73798 25054 28 Locked 256QAM 36 945.00 MHz -1.80 dBmV 37.90 dB 70185 19172 29 Locked 256QAM 37 951.00 MHz -2.10 dBmV 37.30 dB 68195 21809 30 Locked 256QAM 38 957.00 MHz -2.40 dBmV 36.40 dB 71177 23922 31 Locked 256QAM 39 963.00 MHz -1.50 dBmV 36.90 dB 63878 21093 32 Locked 256QAM 40 969.00 MHz -0.80 dBmV 36.90 dB 62724 19128 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 3 5120 kSym/s 30.30 MHz 37.25 dBmV 2 Locked ATDMA 4 5120 kSym/s 36.70 MHz 38.75 dBmV 3 Locked ATDMA 2 5120 kSym/s 23.90 MHz 35.75 dBmV 4 Locked ATDMA 1 5120 kSym/s 17.40 MHz 36.25 dBmV Event Log The table below contains the log of events that the SB6190 has detected. This log can be important to the service provider to help diagnose and correct problems, if any should occur. Top of Form Time Priority Description Wed May 03 05:31:38 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:38:19 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:41:50 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:44:58 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:52:01 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:52:58 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 05:57:06 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 06:23:54 2023 3 No Ranging Response received - T3 time-out;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 06:27:40 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 07:47:07 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 07:52:13 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 07:57:18 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:02:24 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:32:57 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:40:37 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:48:13 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 08:51:32 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 09:18:47 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 09:22:59 2023 5 RCS Partial Service;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0; Wed May 03 11:10:47 2023 3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=98:f7:81:53:xx:xx;CMTS-MAC=84:8a:8d:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;Packet loss in San Diego, CA
I have been experiencing packet losses since February. I have been ping testing with CMD every single day and have noticed that these packet losses I have been getting are completely random. It can last about 1-5 mins to 1-6 hours. I have already contacted COX a few times already and they don't see anything when pinging the modem/router. I have checked the cables on my end, none of them are faulty. Resetting the box and router do nothing. They even gave me a new Modem/router just about a week or 2 ago and this problem still persists. Getting work done is getting to become impossible with these packet losses. I even sent an FCC complaint and haven't heard NOTHING back at all.
High-pitched sound from Cox Gateway
About a month ago, I switched to Cox as my internet service provider. The Cox technician installed a Technicolor CGM4140COM Panoramic Gateway here in the office next to my computer. From the start, the Gateway made a high-pitched humming or whirring sound when running. The sound was very distracting, and after a time when I was working here next to it, my right ear would feel discomfort or pressure. I called Cox to report the problem and was told I could go to the Solution Store and exchange the Gateway. I took it in and was given another CGM4140COM model. I hooked that one up, and it makes the same high-pitched sound as the original one. I now think the original one was not defective, but that all CGM4140COM Gateways make this sound. Have any of you experienced the same problem? If you have, do you have any tips or suggestions for how to remedy the problem? Thanks for your assistance.
Does COX ROBO scan service with high usage and remove DNS / internet service?
Seems Like COX is Robo scan all stream usage and disconnect you from internet, we may be able to prove this, also why does internet disconnect and connect without having them to come as there is nothing wrong with connection. Also i would think they are scanning all not essential and entertainment urls and if that is the case they are disconnecting so it might be some sort of pack order for usage. please comment on my theory if any one else seems to think in same line, . I think to make good case, CPUC may need hard evidence to see what COX Communications doing. may be there is more to it.
85142 - The Internet is always hanging and then connecting again. I consistently see Uncorrectable Errors.
85142 - The Internet is always hanging and then connecting again. I consistently see Uncorrectable Errors on Channels 1,6,7,8, and 9 with Arris SB6183 16-channel modem. I confirmed outside connections are solid where we have an Antronix 4-way 5-1002Mhz splitter with four -7dB out connections. We also have a MoCA POE-F201C filter for the incoming line. No major issues until a recent Cox Outage and now constant issues. Any recommendations?7+ years of summer internet issues and packet loss in Sahuarita/85629.
Question(s): Is there a way to request an inspection / audit / health check of the neighborhood infrastructure? Does having IP addresses help narrow down potential locations? Is there a way to better seal or enclose equipment? I never had these issues over 10 years in the PHX area... and it is an objectively harsher environment for electronic survivability. I'm happy to help be part of the solution for myself and my neighbors… just let me know what I can do. However, having a tech come out to my house and start this debug dance for the 7th year in a row is just going to waste everyone's valuable time yet again. History: Entering year 7 of having summer internet issues. Always at or around monsoon season. Every year I am told that it must be my equipment. Every year a tech gets sent out at least once. Usually multiple times. Every year it takes 30-60 days of back and forth to resolve. It has always been cox equipment somewhere in the neighborhood. I work from home, and find this extremely frustrating. Every year I start all over again like bad internet groundhog day… explaining the history, potential issues, and following the same path of a tech at my door measuring MER and BER. It has never been my equipment… marginal improvement in performance gains. If I had any other reasonable option for internet service at my house, I'd have exercised it years ago. Issue: Here we are again… I was hopeful that maybe things would be different this year. However, there was broad outage in the 85629 area on 06/22/22 from around 0900-1200 AZ. After which, outbound packet loss has been intermittent accompanied by low upload speeds. This morning, my upload speeds have been abysmal. 1Mbps up to around 5Mbps. My normal upload speed is consistently ~35Mbps. Along with that, I am seeing significant packet loss. Outbound packet loss has been anywhere from 3-30%. Inbound speeds are moderately lower than normal, and I am not seeing significant inbound packet loss. Troubleshooting: 1. I've rebooted the router and modem multiple times. 2. I'm using hardwired devices, and have swapped between multiple ethernet cables. CAT5e and CAT6 on the off chance it would do anything. (I knew it wouldn't) 3. I've gone through 2 different routers, flashed the firmware of both routers, and gone direct through the modem. 4. I've used multiple computers to ensure the behavior is not limited to a single computer. 5. Still seeing the same results. Pathping: Shows no packet loss between computer and router, or router and modem. In fact, the first problematic node is 10.97.200.1 … I'm guessing the neighborhood switch, or other infrastructure. Followed immediately by 100.127.78.150, and 100.120.100.40. Ping Plotter confirms pathping's results. My neighbor across the street (who I share a tap with) sees the same frequent issues. One of my other neighbors a few blocks over is unaffected. 0% packet loss, and I believe they were unaffected by the outage on 06/22/22. Boosting my outbound power by adding attenuators has historically shown some level of improvement. 8-12dB has been the sweet spot, but isn't making a difference right now. Hypothesis: I'm going take a wild guess, and say that either the Wednesday worksite was not buttoned up properly after work finished, or another area has significant water ingress after recent monsoon rains. As the day has progressed (and the area potentially dries out), upload speeds and packet loss have improved. Twice now, the summer monsoons have flooded repair sites that were not properly sealed up. Occasionally, packrats get into equipment, and cause havoc.
Way too many service interruptions
This is the third service interruption since Friday. The number of service interruptios in April have gotten ridiculous. Why am I paying for a service I can't even use? It's absolutely unacceptable especially when this is the only service we can get in our area (74107). I work from the home via internet and that is now suffering because our internet service is unreliable. What is going on?