Constant Packet Loss For Years Now.
I have had cox's highest internet plan for as long as I can remember. I have had countless techs in my home including multiple maintenance escalation tickets called out for my issues. Still nothing changes. Every time I call to discuss the same issue, I get the same answers and have to fight to get escalated to a higher tier support so that someone understands what I am experiencing. I now chart all of my packet loss and am building a portfolio to seek legal action. I have the gigablast package which runs me $120.00 per month and can only use the internet efficiently approximately 35% of the time. As I am writing this post I have been incurring packet loss and disconnections for the past 3 hours. If a high tier cox tech would like to look into my account and see how many techs and issues I have had at my address, please do. I am going to keep posting all of my data graphs and information on the forums as calling and trying to get this settled is not working. All I can say is this has been an issue for years in my location and if I had the opportunity to switch providers, I would have left cox a long time ago. Please help! https://imgur.com/a/u0UVYJJ441Views0likes2CommentsNetwork disconnection
Almost daily there is a drop in both wired and wireless connections and this has been the “as per usual”from Cox with every single reply of “ It must be your equipment” and then they would claim firmware updates or that the line has feedback from another uncapped line outside my property. Has anyone else had this same issue? Each time I formally complain at the customer care . I have the gigablast and panoramic wifi887Views0likes2CommentsFrequent internet disconnects/modem reboots due to bad signal
Hey all, I'm specifically looking for someone higher up at Cox to help me out here. I just moved into a new apartment with my girlfriend and signed up for a 100/10 internet plan. I bought a brand new Netgear CM600 cable modem and a router and set them up when we moved in and provisioned the modem and all seemed good, but I noticed our downstream power levels were a bit strange; the first 16 channels were ~18 dBmV and the last 8 were ~ -17 dBmV. I did some research and seems like these levels are supposed to be around 0, with a range of -10 to 10 dBmV. No problem, I'm an engineer at a satellite communications company and have plenty of attenuators at work. Grabbed a few and have been experimenting with different values, got the levels to 7 dBmV but we were still getting a ton of correctables on the downstream channels and frequent disconnects. I caved and had a technician come by today but right off the bat I knew he wasn't going to be too helpful. He switched out the coaxial cable to the modem and put an attenuator on it, then showed me on his phone that all the downstream channels were green and had "stabilized". I asked if he could take a look at the connections to the apartment but he refused. It's been ~6 hours since he's left and we're still having disconnects and the modem is rebooting. Find screenshots of my power levels and event logs below, about half an hour after manually rebooting the modem. I was going to wait a couple days before scheduling another tech visit but I don't want to go through this process again when there's a chance of getting another tech who isn't going to do anything I haven't already done. I know it's not the tech's fault, so I was still very polite to him, but I really need this issue to be resolved ASAP! So please, if there are any Cox employees on here who would be able to help me look into this, I'd be very appreciative 🙂 Thank you so much in advance!4.8KViews0likes3CommentsHigh Uncorrectable Errors
Hi All, Ive been having really crappy internet for the last few weeks and a check of my modem status page shows the following uncorrectable errors on channels 13, 14 and 15. Cox say they dont see these on their side. Please bear in mind this is in two hours of usage from a reboot. Any recommendations? Standard Specification Compliant ARRIS DOCSIS 3.0 Cable Modem / Retail Hardware Version 3 Software Version 9.1.103AA36 Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Corrected Uncorrectables 1 Locked 256QAM 3 795.00 MHz 4.10 dBmV 38.98 dB 1 0 2 Locked 256QAM 1 783.00 MHz 4.70 dBmV 38.98 dB 0 0 3 Locked 256QAM 2 789.00 MHz 4.70 dBmV 38.98 dB 0 0 4 Locked 256QAM 4 801.00 MHz 4.20 dBmV 38.98 dB 4 0 5 Locked 256QAM 9 831.00 MHz 4.60 dBmV 38.98 dB 0 0 6 Locked 256QAM 10 837.00 MHz 4.30 dBmV 38.61 dB 0 0 7 Locked 256QAM 11 843.00 MHz 4.40 dBmV 38.98 dB 1 0 8 Locked 256QAM 12 849.00 MHz 4.20 dBmV 38.61 dB 1 0 9 Locked 256QAM 17 879.00 MHz 3.60 dBmV 38.98 dB 6 0 10 Locked 256QAM 18 885.00 MHz 3.80 dBmV 38.61 dB 3 0 11 Locked 256QAM 19 891.00 MHz 3.90 dBmV 38.61 dB 19 0 12 Locked 256QAM 20 897.00 MHz 4.00 dBmV 38.61 dB 20 0 13 Locked 256QAM 21 903.00 MHz 3.80 dBmV 38.61 dB 63278 558593 14 Locked 256QAM 22 909.00 MHz 3.90 dBmV 38.61 dB 109054 1166810 15 Locked 256QAM 25 927.00 MHz 4.10 dBmV 38.61 dB 81462 719967 16 Locked 256QAM 26 933.00 MHz 3.90 dBmV 38.61 dB 11 0 17 Locked 256QAM 27 939.00 MHz 4.20 dBmV 38.98 dB 14 0 18 Locked 256QAM 28 945.00 MHz 3.70 dBmV 38.98 dB 0 0 19 Locked 256QAM 29 951.00 MHz 3.60 dBmV 38.61 dB 0 0 20 Locked 256QAM 30 957.00 MHz 3.60 dBmV 38.61 dB 0 0 21 Locked 256QAM 33 357.00 MHz 6.20 dBmV 40.37 dB 0 0 22 Locked 256QAM 34 363.00 MHz 6.20 dBmV 40.95 dB 7 0 23 Locked 256QAM 35 369.00 MHz 6.40 dBmV 40.37 dB 0 0 24 Locked 256QAM 36 375.00 MHz 6.30 dBmV 40.37 dB 3 0 25 Locked 256QAM 37 381.00 MHz 6.40 dBmV 39.90 dB 0 0 26 Locked 256QAM 38 387.00 MHz 6.30 dBmV 39.90 dB 0 0 27 Locked 256QAM 41 405.00 MHz 6.40 dBmV 39.90 dB 0 0 28 Locked 256QAM 42 411.00 MHz 6.60 dBmV 39.90 dB 0 0 29 Locked 256QAM 43 417.00 MHz 6.40 dBmV 39.90 dB 0 0 30 Locked 256QAM 44 423.00 MHz 6.50 dBmV 39.90 dB 0 0 31 Locked 256QAM 45 429.00 MHz 6.20 dBmV 40.40 dB 0 0 32 Locked 256QAM 46 435.00 MHz 6.30 dBmV 39.90 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 2 5120 kSym/s 23.50 MHz 40.25 dBmV 2 Locked ATDMA 4 5120 kSym/s 36.30 MHz 42.25 dBmV 3 Locked ATDMA 3 5120 kSym/s 29.90 MHz 40.25 dBmV 4 Locked ATDMA 1 5120 kSym/s 16.90 MHz 40.25 dBmV6.1KViews0likes6CommentsIncreasing 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.2KViews0likes4CommentsHigh Upstream Power levels
DVW326B Cable modem via Cox constant disconnects, at least 10-15 times daily, Cox Tech sub contractor has been out, I've replaced the Modem 4 times now with no results, Researching this issue I found information stating that 51-54 DbmV is quite high for an Upstream signal power level depending on what channel I'm looking at.. My modem is essentially screaming at the isp and eventually shutting down My downstream seems to be o.k. at -4.7 - -6.0 although it should be 0 Why hasn't Cox detected this in all the times they have looked into my modem connection or the tech when he came out I need this resolved immediately1.9KViews0likes1CommentSending an email to COX, I would like a resolution.
To whom it may concern, I want to start by saying that I am EXTREMLY DISAPPOINTED with my COX internet service. First, I would like to point out that I have recently moved from a location in Scottsdale, Arizona to Anthem, Arizona. Since my move, I have had nothing but problems with my internet. COX has been my service provider for around the last 15 years, for entertainment, business, and educational needs. There has always been little issues that would come up here or there and then get resolved. However, it seems of the last three years or so I have struggled with my internet connection more and more. It takes time to call, troubleshoot, setup appointment and schedule all of it between more important tasks in my life. Currently I pay for the premium internet service. From what I understood in the last couple of emails that I received about the upgrades it that my internet service was supposed to double. This seemed very exciting and reasonable considering the amount of money I pay for the premium service. The speed was supposed to be up to 100MB down and I figured that there would be a decent increase in upload as well. This actually was working fine before I moved; my service would range from 80 – 100 down on average and 8 – 12 up. This is an acceptable range, of course I am not getting 100 down 100% of the time but 20% decrease during busy hours was acceptable. Since moving to my new home in Anthem, I have had nothing but problems. All my computers, OS’s and equipment are identical but my speed on average has been lower than the next lower tier service. I see latency problems, drops in speed, disconnects, and on average I am getting bellow 50MB down. Why am I paying for a higher tier of service only to get speeds less than the next lower tier? COX technicians have been to my house looking into the problem, they tell me it is my computer or my cable modem. However, I have switched out the cable modem, I have bypassed my router, I have tried different computers and laptops, and still the same intermittent problems. The last COX technical representative was even making changes to my registry on my personal compute when I was not home and my fiancé was there for the appointment. At this point, I am an extremely dissatisfied customer and expect someone in your company to come up with a permanent solution to this problem. It does not make sense that I am paying for a premium service, with line insurance, etc. and have to deal with an intermittent problem such as this.1.9KViews0likes1CommentAnother multiple disconnect issue
This getting to be more than irritating as it's been going on for literally years and since the boost in speed has gotten worse. I keep getting disconnected. I'll let the current log speak as it is representative of a common disconnect. Now the apartment has had the cable coming in replaced and all of the equipment check and it's all good. This issue seems to be local to the build ing I am in. Modem i9s an SB6180 2014-02-08 12:26:52 3-Critical SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within ti 2014-02-08 12:26:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:26:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:43 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:26:41 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:27 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:26:27 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:11 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:26:10 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:26:05 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:26:05 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:25:39 5-Warning MDD message timeout;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM-QOS=1 2014-02-08 12:25:22 5-Warning Dynamic Range Window violation 2014-02-08 12:25:13 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM 2014-02-08 12:25:13 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:b1:2e; 2014-02-08 12:24:53 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:24:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:23:50 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:23:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 12:23:30 6-Notice Ds Lock Failed - Reinitialize MAC... 2014-02-08 12:23:30 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 12:23:26 6-Notice Ds Lock Failed - Reinitialize MAC... 2014-02-08 12:22:57 6-Notice TLV-11 - unrecognized OID;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12:d9:54:8f:ce;CM 1970-01-01 00:03:02 5-Warning ToD request sent - No Response received;CM-MAC=a4:7a:a4:fe:b1:2e;CMTS-MAC=00:12: 1970-01-01 00:02:57 5-Warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=a4:7a:a4:fe:b1:2e; 1970-01-01 00:02:39 3-Critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC= 1970-01-01 00:02:26 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:02:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:02:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:01:56 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:01:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:01:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:01:22 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:01:21 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 1970-01-01 00:01:20 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 1970-01-01 00:00:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:44:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:44:22 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:43:58 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:43:56 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:43:38 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:43:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:43:32 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:36 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:42:36 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:21 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:42:21 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:19 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:42:17 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:42:13 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:42:11 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:42:11 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:41:44 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:41:40 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:41:38 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:41:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:41:07 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:40:59 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:40:34 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:40:16 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:39:29 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:38:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:38:47 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:38:38 3-Critical TFTP Request Retries exceeded, CM unable to register 2014-02-08 11:38:12 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:36:12 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:36:10 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:36:08 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:36:02 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:36:02 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:35:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:34:54 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:34:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:34:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:34:46 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:27:52 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:27:48 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:27:44 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 11:17:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:17:33 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:17:29 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:10:25 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:06:09 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 11:03:46 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 11:01:05 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 10:56:13 3-Critical TFTP Request Retries exceeded, CM unable to register 2014-02-08 10:55:49 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 10:52:13 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:43:32 3-Critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o 2014-02-08 10:36:57 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 10:35:49 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:35:45 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 10:35:39 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:35:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:20:24 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:41 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; 2014-02-08 10:09:37 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:31 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:26 3-Critical SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=a4:7a 2014-02-08 10:09:14 3-Critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; ©2004 Motorola All rights reserved. And this is just for today. Will someone get this fixed please? or tell me what I need to do to fix it.I am tired of calling the tech support as most of them seem to be just script readers with no real knowledge of networking.3.2KViews0likes5CommentsPacket Loss During Peak Times with Ultimate Tier
I've been experiencing excess packet loss during the evening for the past few weeks. This causes frequent disconnects in online games as well as excess lag. At around 7:00pm today: Tracing route to cox.net [68.99.123.161] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 10 ms 7 ms 8 ms 10.0.16.1 3 7 ms 8 ms 7 ms 68.1.8.229 4 8 ms 13 ms 9 ms 68.1.8.207 5 26 ms 8 ms 9 ms 68.1.8.86 6 16 ms 11 ms 11 ms dukedsrj02-ge210.0.rd.at.cox.net [68.1.1.123] 7 12 ms 30 ms 12 ms 68.1.15.238 8 * 11 ms 10 ms 68.99.123.4 9 12 ms 12 ms 11 ms ww2.cox.com [68.99.123.161] Trace complete. C:\Users\Matthew>ping cox.net -t Pinging cox.net [68.99.123.161] with 32 bytes of data: Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Request timed out. Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=10ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=16ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=13ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=10ms TTL=56 Reply from 68.99.123.161: bytes=32 time=13ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Request timed out. Reply from 68.99.123.161: bytes=32 time=10ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=13ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Request timed out. Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=12ms TTL=56 Reply from 68.99.123.161: bytes=32 time=11ms TTL=56 Ping statistics for 68.99.123.161: Packets: Sent = 34, Received = 31, Lost = 3 (8% loss), Approximate round trip times in milli-seconds: Minimum = 10ms, Maximum = 16ms, Average = 11ms I also ran PingPlotter against the FFXIV ARR server that I play on as well as on cox.net. FFXIV ARR - http://imgur.com/nZyC6sV COX.net - http://imgur.com/ZJm4BmS I've also uploaded my signal page from my modem (SB6141). http://imgur.com/eLhW0zA5.9KViews0likes6CommentsInternet Connection Dropped - Netgear Router Settings
Is there a certain setting that needs to be enable/disabled for the Netgear Routers? I have run the setup feature using the Netgear Genie still losing the internet connection. Moved to the current house in November, used the same cox provided Netgear Router from previous address that worked great. Router at the home began to drop internet connection. Wireless devices are still connected to the router as well as hard wire computer, no internet connection. Have to reboot the router. Upgraded to a new Netgear Router. Same problem is still happening. I have to reset the router through the Netgear Genie. Cox support says the internet connection has not been lost must be the router. Make me sign up for the Networking support just to talk to a networking specialist and she offered nothing. Anyone have this same problem with the Netgear Routers?54KViews0likes24Comments