Frequent but not Constant Incredibly High Ping and Packet Loss
I have contacted support twice with this issue already. The first time, the support agent said there was an outage due to overloaded nodes, which is what I had heard online. But this happens even when there is no outage. I have multiple PingPlotter screenshots attached to this post. My computer is plugged directly into the modem, and we have 1.1ms ping to the modem, so that is not the issue. I have restarted my modem already, and that did not fix the issue. It makes online video games unplayable. It also effects other devices. While I was experiencing lag spikes on my computer, I ran a speedtest on my phone and got 60mbps and 82 ping on a test that normally shows 160+ mbps and 5-15 ping. The first time, support said they could not send a technician during the outage, and we would need to document the issue occurring afterwards. After I did, I contacted support a second time, and they said they would need to document it on their own speedtests, which is not possible as I have to wait on hold for 15 minutes, and by that time, the issue usually resolves. They said in that case I should post screenshots here. So here they are. If nothing happens, I may file an FCC complaint, as that seems like the only thing that can get this company to do anything. Here are some images. https://imgur.com/a/iNfur3A
Been having horrible packet loss, low speeds, and high latency
For the last what feels like 6 months, I've been getting worse and worse performance from my internet, with no end in sight. I often online game, and with the network stats that I get, its been getting less and less playable. I had a tech come out to see and they fixed one of my cables, but it didn't seem to fix anything. I was wondering if anyone could look at my logs and my modem stats to maybe give me a starting point to what could be the problem. Thanks in advance to anyone that might could help. My starting freq. is405000000. And I'm using a CM1000. ApplyCancel Frequency start Value This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect. Starting Frequency <tabindex=-1>Startup Procedure Procedure Status Comment Acquire Downstream Channel 849000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Honor MDD IPv4 only <tabindex=-1>Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 12 849000000 Hz 4.8 dBmV 40.6 dB 68062417 0 0 2 Locked QAM256 1 783000000 Hz 3.9 dBmV 40.4 dB 89915226 0 0 3 Locked QAM256 2 789000000 Hz 4.0 dBmV 40.5 dB 89918531 0 0 4 Locked QAM256 3 795000000 Hz 3.7 dBmV 40.4 dB 89922348 0 0 5 Locked QAM256 4 801000000 Hz 4.0 dBmV 40.4 dB 89926080 0 0 6 Locked QAM256 9 831000000 Hz 4.5 dBmV 40.6 dB 89929701 0 0 7 Locked QAM256 10 837000000 Hz 4.7 dBmV 40.6 dB 89933515 0 0 8 Locked QAM256 11 843000000 Hz 4.6 dBmV 40.6 dB 89937132 0 0 9 Locked QAM256 41 405000000 Hz 3.9 dBmV 40.8 dB 67234001 0 0 10 Locked QAM256 17 879000000 Hz 5.4 dBmV 40.5 dB 89944411 0 0 11 Locked QAM256 18 885000000 Hz 5.6 dBmV 40.5 dB 89948472 0 0 12 Locked QAM256 19 891000000 Hz 5.6 dBmV 40.5 dB 89952238 0 0 13 Locked QAM256 20 897000000 Hz 5.8 dBmV 40.5 dB 89955493 0 0 14 Locked QAM256 21 903000000 Hz 5.8 dBmV 40.5 dB 89958669 452 208 15 Locked QAM256 22 909000000 Hz 5.6 dBmV 40.5 dB 89963211 0 0 16 Locked QAM256 25 927000000 Hz 3.5 dBmV 40.1 dB 89966356 473 156 17 Locked QAM256 26 933000000 Hz 2.2 dBmV 39.8 dB 89970231 0 0 18 Locked QAM256 27 939000000 Hz 3.2 dBmV 40.1 dB 89974303 0 0 19 Locked QAM256 28 945000000 Hz 4.4 dBmV 40.4 dB 89977845 0 0 20 Locked QAM256 29 951000000 Hz 5.2 dBmV 40.8 dB 89981626 0 0 21 Locked QAM256 30 957000000 Hz 4.9 dBmV 40.7 dB 89985268 0 0 22 Locked QAM256 33 357000000 Hz 3.6 dBmV 40.6 dB 89989162 0 0 23 Locked QAM256 34 363000000 Hz 3.5 dBmV 40.8 dB 89992954 0 0 24 Locked QAM256 35 369000000 Hz 3.6 dBmV 40.8 dB 89996247 0 0 25 Locked QAM256 36 375000000 Hz 3.5 dBmV 40.7 dB 90000331 0 0 26 Locked QAM256 37 381000000 Hz 3.6 dBmV 40.8 dB 90003895 0 0 27 Locked QAM256 38 387000000 Hz 3.5 dBmV 40.6 dB 90007726 0 0 28 Locked QAM256 42 411000000 Hz 3.9 dBmV 40.8 dB 90011488 0 0 29 Locked QAM256 43 417000000 Hz 3.9 dBmV 40.7 dB 90015408 0 0 30 Locked QAM256 44 423000000 Hz 3.9 dBmV 40.7 dB 90018264 0 0 31 Locked QAM256 45 429000000 Hz 3.9 dBmV 40.7 dB 90020237 0 0 32 Locked QAM256 46 435000000 Hz 4.0 dBmV 40.7 dB 90020121 0 0 <tabindex=-1>Upstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 1 17700000 Hz 38.5 dBmV 2 Locked ATDMA 2 24100000 Hz 38.0 dBmV 3 Locked ATDMA 3 30500000 Hz 39.0 dBmV 4 Locked ATDMA 4 36900000 Hz 39.5 dBmV 5 Locked ATDMA 6 12900000 Hz 38.3 dBmV 6 Not Locked Unknown 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Hz 0.0 dBmV <tabindex=-1>Downstream OFDM Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0, 3 159 300000000 Hz 7.6 dBmV 41.8 dB 1108 ~ 2987 105783337 49080316 0 2 Not Locked 0 0 0 Hz -36.2 dBmV 0.0 dB 0 ~ 4095 0 0 0 <tabindex=-1>Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked Unknown 0 0 Hz 0 dBmV 2 Not Locked Unknown 0 0 Hz 0 dBmV Time Priority Description 2020-06-08, 12:41:47 Warning (5) Dynamic Range Window violation 2020-06-08, 12:41:47 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-06-08, 12:41:40 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-06-08, 12:29:24 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 3.;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-06-08, 12:29:19 Notice (6) TLV-11 - unrecognized OID;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-06-08, 12:29:19 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4 Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-05-23, 09:01:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-05-21, 05:00:54 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-05-19, 20:14:49 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:39:56 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:39:56 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:39:52 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:39:52 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:16:05 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:15:49 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:15:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:15:21 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:14:49 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:14:10 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:14:09 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:13:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:13:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:13:22 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:13:20 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:13:11 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:13:10 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:12:51 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:12:50 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:12:50 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:12:37 Critical (3) Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:12:33 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:12:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-23, 00:11:49 Critical (3) SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1; 2020-04-20, 19:17:39 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:0c:6b:ca:58:50;CMTS-MAC=00:59:dc:78:e5:cd;CM-QOS=1.1;CM-VER=3.1;
Why have your prices climbed when your service is unusable?
Your prices have climbed so high. We have had cox for a long time like 10+ years, and your prices have only gotten higher while your service has degraded. I had problems with latency, ping, and jitter even before corona. I got tired of doing the run around, but its so sad that with all the revenue from overselling your Nodes and hiking prices; the company was never able to upgrade their infrastructure. A lot of people are filing FCC complaints, and I hope it does something ( I doubt it.) I cant even go to class without getting Packet loss. Its futile. The worst part is, the company is policing the threads, and we cant even voice our concern. I understand its your company, but its OUR money that your taking. You are liable to delivering that service.
High Pings and Jitters along with Packet Loss
Hi all, I have been having high pings and large packet loss every single day for the past 2 months (before the COVID-19 outbreak), and have had bufferbloat every time I connect to wifi. I thought the problem was with the Ethernet and hence bought a new wire to test yet this problem persisted. The following is my trace route to google: Tracing route to www.google.com [2607:f8b0:4007:804::2004] over a maximum of 30 hops: 1 2 ms 2 ms 2 ms 2600:8800:802:900:120c:6bff:fe78:2352 2 56 ms 52 ms 39 ms 2600:8800:87f:ffff::1111 3 * 12 ms * 2001:578:801:fffc::e 4 202 ms 38 ms 77 ms 2001:578:800:4:9800::2 5 33 ms 55 ms * 2001:578:1:0:172:17:249:33 6 49 ms 39 ms 26 ms 2001:4860:1:1::131a 7 34 ms 59 ms 26 ms 2607:f8b0:820d::1 8 29 ms 31 ms 38 ms 2001:4860:0:110f::1 9 31 ms 28 ms 25 ms 2001:4860:0:110f::13 10 24 ms 43 ms 37 ms 2001:4860::c:4000:de3c 11 * 30 ms * 2001:4860::9:4000:de3b 12 23 ms 72 ms 67 ms 2001:4860:0:1::1039 13 26 ms 44 ms 35 ms lax28s15-in-x04.1e100.net [2607:f8b0:4007:804::2004] Trace complete. The third hop almost always times out and I have no idea why. Please let me know what I can do, I have tried everything contacted all technicians but they have not been able to figure out anything. I currently use a 150mbps residential connection with a Netgear C6250 router modem.Intermittent ping fluctuation and packet loss LAS VEGAS
Hello, For the pastmonth or twoI've been experiencing episodes of high ping and sometimes packet loss. They happen every3-10 mins or so. During this time gaming is very unstable. I believe my modem signal levels are good. Cabling is from 2013 (new construction). I only have internet, no TV. There are about6 sets of errors(warnings) a day on the modem itself. They are: Warning (5) Dynamic Range Window violation Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1; What I have tried: New Modem Bypassing router directly to modem Removing ALL splitters Cable comes from underground to the box on the side of my house That cable couples using a MOCA filter (though i've tried without the filter) directly to a cable that goes to the modem There is a 10DB attenuator on the cable before going into the modem I've tried 3DB and 6DB pads as well. I have a Netgear CM1000 (brand new). I believe the problem is at the node but am open to suggestions thatIhave control over if you have them. Ping Plotter: https://imgur.com/1rVQVjW https://imgur.com/TNzHkve Modem stats and errors (System Up Time:69:09:24) https://imgur.com/pMrlFmr https://imgur.com/z9OoEj2Periods of high latency & extremely slow speeds
Problem seems to have started popping up last tThursday, but since then my house seems to have periods of time where the network speed slows the a crawl andI'm barely able to use the network (and definitely unable to run any multiplayer games). I've tried a bunch of different simple fixes but to no avail, so I'm at a loss on what I should try next. Setup information: Modem/Router: AC1750 Wifi Cable Modem Model Wiring: Underground, resedential neighborhood Affected Connections: Wired and wireless Normal Speeds (wired): ~50 to 100 mbps download and 30ish upload Speeds during a bout of slowness: ~0.3 mbps download and 0.6 mbps upload What I've tried already Resetting the modem/router (on my end) Factory resetting the modem/router , netgear admin page shows connection is 'good' Unplugging the modem/router and waiting 3-5 minutes to plug back in Resetting the modem/router (on coxs end) Disabling wireless and testing only my wired connection Useful info? I noticed in this thread a guy says anything over 1-2ms on a ping to 192.168.0.1 is a problem, and here is my ping output: Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time=6ms TTL=64 Reply from 192.168.0.1: bytes=32 time=3ms TTL=64 Reply from 192.168.0.1: bytes=32 time=10ms TTL=64 Reply from 192.168.0.1: bytes=32 time=7ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 10ms, Average = 6ms Here is also my connection information which I grabbed from my netgear admin panel: Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables UnCorrectables 1 Locked QAM 256 9 831000000 Hz 13.3 dBmV 38.6 dB 310 0 2 Locked QAM 256 10 837000000 Hz 13.1 dBmV 38.6 dB 324 0 3 Locked QAM 256 11 843000000 Hz 13.4 dBmV 38.9 dB 237 0 4 Locked QAM 256 12 849000000 Hz 13.0 dBmV 38.9 dB 246 0 5 Locked QAM 256 13 855000000 Hz 13.3 dBmV 38.9 dB 203 0 6 Locked QAM 256 14 861000000 Hz 13.1 dBmV 38.9 dB 196 0 7 Locked QAM 256 15 867000000 Hz 13.5 dBmV 38.9 dB 131 0 8 Locked QAM 256 16 873000000 Hz 13.0 dBmV 38.9 dB 128 0 9 Locked QAM 256 25 927000000 Hz 13.0 dBmV 38.9 dB 40 0 10 Locked QAM 256 26 933000000 Hz 12.9 dBmV 38.9 dB 47 0 11 Locked QAM 256 27 939000000 Hz 12.4 dBmV 38.6 dB 49 0 12 Locked QAM 256 28 945000000 Hz 11.9 dBmV 38.9 dB 52 0 13 Locked QAM 256 29 951000000 Hz 12.0 dBmV 38.6 dB 28 0 14 Locked QAM 256 30 957000000 Hz 12.0 dBmV 38.9 dB 9 0 15 Locked QAM 256 31 963000000 Hz 12.5 dBmV 40.3 dB 2 0 16 Locked QAM 256 32 969000000 Hz 12.3 dBmV 38.9 dB 8 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 4 2560 Ksym/sec 18400000 Hz 44.3 dBmV 2 Locked ATDMA 3 5120 Ksym/sec 23300000 Hz 44.3 dBmV 3 Locked ATDMA 2 5120 Ksym/sec 29800000 Hz 44.3 dBmV 4 Locked ATDMA 1 5120 Ksym/sec 36300000 Hz 44.3 dBmV Lastly, here's a tracert of google.com: Tracing route to google.com [2607:f8b0:4007:80d::200e] over a maximum of 30 hops: 1 4 ms 9 ms 6 ms 2600:8801:2980:81d:a02:8eff:fec6:6662 2 245 ms 119 ms 318 ms 2600:8801:29ff:ffff::1111 3 427 ms * 82 ms 2001:578:601:fffc:500::1c 4 24 ms 143 ms 30 ms 2001:578:604::1a 5 65 ms 48 ms 42 ms 2001:578:1:0:172:17:249:79 6 59 ms 110 ms 77 ms 2001:578:20:c100::5:1 7 184 ms 235 ms 48 ms 2001:4860:0:1004::e 8 43 ms 89 ms 59 ms 2001:4860::c:4001:13cf 9 45 ms 49 ms 309 ms 2001:4860::c:4000:de3d 10 215 ms 49 ms 332 ms 2001:4860::1:0:c432 11 * 78 ms 132 ms 2001:4860:0:110d::1 12 185 ms 94 ms 36 ms 2001:4860:0:1::1f01 13 372 ms 259 ms 50 ms lax28s10-in-x0e.1e100.net [2607:f8b0:4007:80d::200e] Trace complete. Any ideas on what I should try?
