2 Messages

Saturday, August 15th, 2026 9:17 PM

UCG Max detecting High Latency, dropped packets, and disconnected services from Xfinity

I have a Ubiquiti Cloud Gateway Max connected to a CM3000. I recently upgraded from a S33 as the UCG was giving alerts that I had high latency coming from Xfinity. My thought was that the S33 was just old and needed replaced. After replacing it with the CM3000, I upgraded to the 1 Gig plan and hoped the issue would be resolved. Every other day now, I get High latency (1000+ ms), dropped packets, and about 5 minute disconnections. After checking my network, I reluctantly scheduled an appointment for a tech to come look at the issue. While he could not find any present issues or downtime, he proceeded to tell me that my switches were causing issues and that I needed to get the Xfinity equipment instead. 

Has anyone else experienced these kinds of issues? If so, what solutions did you find? My thought was that the rain or wind was messing with an open line somewhere causing some kind of fault or error. Another thought is that somewhere a piece of equipment is becoming faulty.

Also, has anyone experienced a technician who won't listen to the issue and just wants to blame your equipment? If I wanted that I would just use the Chat Bot. Apparently we only need their equipment so we can stream Netflix and play games (said the tech). My VLAN networks for my Servers are not necessary (said the tech). I have been working in tech for a long time and studied each aspect of it in school (BASc). I enjoy what I do and am looking for support with an issue I am having, not an argument from someone who doesent know what Ubiquiti is or how a Cisco switch works.

Any insight as to why this would be happening without any trace on Xfinity's end?

Here is what I am seeing that Xfinity can't see:

Internet connection WAN1 (Comcast Cable) on port 5 is experiencing high latency.

Internet connection WAN1 (Comcast Cable) on port 5 is restored after a temporary disconnection.

Internet connection WAN1 (Comcast Cable) on port 5 is experiencing packet loss.

Internet connection WAN1 (Comcast Cable) on port 5 is down.

Cable Diagnostic

Status: Good

Action:
Your setup looks fine. If you can't access the internet, make sure you properly activated the modem. If modem has been activated and you still can't access the internet, contact your service provider for troubleshooting help.
If you can access the internet but has other internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.

CM Status: Good

Downstream Status: Good

    Downstream Power Level: Good

    Downstream SNR Level: Good

Upstream Status: Good

    Upstream Power Level: Good


Current Time: Sat Aug 15 14:02:42 2026

Startup Procedure
Acquire Downstream Channel: 495000000 Hz  Locked
Connectivity State:          OK       Operational
Boot State:                  OK       Operational
Security:                   Enabled   BPI+
IP Provisioning Mode:       Honor MDD   IPv6 only


Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID  Frequency     Power    SNR   Correctables Uncorrectables     
      1     Locked     QAM256     20     495000000 Hz     -1.6     44.5     0     0
      2     Locked     QAM256     13     453000000 Hz     -2.1     44.3     0     0
      3     Locked     QAM256     14     459000000 Hz     -2.1     44.3     0     0
      4     Locked     QAM256     15     465000000 Hz     -1.8     44.4     0     0
      5     Locked     QAM256     16     471000000 Hz     -1.8     44.4     0     0
      6     Locked     QAM256     17     477000000 Hz     -1.5     44.6     0     0
      7     Locked     QAM256     18     483000000 Hz     -1.5     44.5     0     0
      8     Locked     QAM256     19     489000000 Hz     -1.4     44.6     0     0
      9     Locked     QAM256     21     501000000 Hz     -1.4     44.5     0     0
     10     Locked     QAM256     22     507000000 Hz     -1.5     44.5     0     0
     11     Locked     QAM256     23     513000000 Hz     -1.4     44.6     0     0
     12     Locked     QAM256     24     519000000 Hz     -1.5     44.5     0     0
     13     Locked     QAM256     25     525000000 Hz     -1.4     44.5     0     0
     14     Locked     QAM256     26     531000000 Hz     -1.6     44.4     0     0
     15     Locked     QAM256     27     537000000 Hz     -1.6     44.3     0     0
     16     Locked     QAM256     28     543000000 Hz     -1.7     44.2     0     0
     17     Locked     QAM256     29     549000000 Hz     -1.8     44.1     0     0
     18     Locked     QAM256     30     555000000 Hz     -1.8     44.1     0     0
     19     Locked     QAM256     31     561000000 Hz     -1.8     44.1     0     0
     20     Locked     QAM256     32     567000000 Hz     -1.7     44.1     0     0
     21     Locked     QAM256     33     573000000 Hz     -1.8     44     0     0
     22     Locked     QAM256     34     579000000 Hz     -1.8     44     0     0
     23     Locked     QAM256     35     585000000 Hz     -1.8     44.1     0     0
     24     Locked     QAM256     36     591000000 Hz     -1.8     44.1     0     0
     25     Locked     QAM256     37     597000000 Hz     -1.9     44     0     0
     26     Locked     QAM256     38     603000000 Hz     -1.9     44     0     0
     27     Locked     QAM256     39     609000000 Hz     -2     43.9     0     0
     28     Locked     QAM256     40     615000000 Hz     -1.9     43.9     0     0
     29     Locked     QAM256     41     621000000 Hz     -2     43.9     0     0
     30     Locked     QAM256     42     627000000 Hz     -1.8     44     0     0
     31     Locked     QAM256     43     633000000 Hz     -1.9     43.9     0     0
     32     Locked     QAM256     44     639000000 Hz     -1.8     43.7     0     0

Upstream Bonded Channels
Channel   LockedStatus  ChannelType ChannelID   SymbolRate        Frequency       Power     
      1       Locked       ATDMA     18       5120 Ksym/sec       22800000 Hz       44.8 dBmV
      2       Locked       ATDMA     17       5120 Ksym/sec       16400000 Hz       44.5 dBmV
      3       Locked       ATDMA     19       5120 Ksym/sec       29200000 Hz       45.0 dBmV
      4       Locked       ATDMA     20       5120 Ksym/sec       35600000 Hz       45.3 dBmV
      5       Not Locked       Unknown      0       0       0       0.0
      6       Not Locked       Unknown      0       0       0       0.0
      7       Not Locked       Unknown      0       0       0       0.0
      8       Not Locked       Unknown      0       0       0       0.0

Downstream OFDM Channels
Channel   LockedStatus  ProfileID  ChannelID    Frequency       Power       SNR/MER    ActiveSubcarrier    Unerror    Correctable   Uncorrectable
      1     Locked     0 ,1 ,2 ,3     193     722000000 Hz     -2.12 dBmV     43.1 dB     388 ~ 3707     91865814     51484622     0
      2     Locked     0 ,1 ,2 ,3     194     957000000 Hz     -3.42 dBmV     41.6 dB     148 ~ 3947     122226736     57517081     0

Upstream OFDMA Channels
Channel   LockedStatus    ProfileID    ChannelID    Frequency       Power
      1     Locked     12 ,13     43     36200000 Hz     40.3 dBmV
      2     Not Locked     0      0     0 Hz     0 dBmV

Event Log
         Time               Priority     Description
Sat Aug 15 12:48:59 2026     Notice (6)     DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 15 12:48:58 2026     Notice (6)     DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 15 12:48:52 2026     Notice (6)     TLV-11 - unrecognized OID;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Time Not Established     Notice (6)     Honoring MDD; IP provisioning mode = IPv6
Time Not Established     Critical (3)     SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 15 01:00:08 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Fri Aug 14 01:45:59 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 11 16:56:10 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 11 05:05:32 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Mon Aug 10 04:55:59 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 08 05:05:09 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Thu Aug 06 23:33:07 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Thu Aug 06 04:04:01 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Aug 04 14:56:50 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 31 05:03:27 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 30 22:06:23 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 30 22:05:26 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Jul 28 12:16:30 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Jul 28 05:02:27 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sun Jul 26 07:29:02 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 24 05:02:05 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 23 12:39:37 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 22 05:01:36 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Jul 21 05:02:02 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Mon Jul 20 05:01:37 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sun Jul 19 21:52:32 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 18 11:07:24 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 18 05:26:27 2026     Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Sat Jul 04 10:59:03 2026     Critical (3)     No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Fri Jul 03 04:59:44 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Thu Jul 02 04:59:39 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;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=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 01 21:36:17 2026     Critical (3)     Resetting the cable modem due to docsDevResetNow
Wed Jul 01 18:06:57 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Wed Jul 01 04:59:10 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Jun 30 22:53:18 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Jun 30 19:37:18 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
Tue Jun 30 04:58:51 2026     Critical (3)     Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Oldest First
Selected Oldest First

Official Employee

 • 

3.6K Messages

17 hours ago

 

dkburd Thanks for sharing these signal levels. From what I can see, the downstream and upstream levels currently look within a healthy range, and the modem is locked onto the expected channels. However, the event log does show several T3 timeout errors over time, which can indicate intermittent communication issues between the modem and the network. These types of errors may not always show up in the signal levels at the exact moment we check them, especially if the issue is intermittent.

I would recommend checking that the coax connection is secure at the modem and wall outlet, and removing any unnecessary splitters if possible. Have you checked that already? Since the logs show repeated T3 timeouts over multiple dates, this may need further review from our side or a technician visit if the connection issues continue.

 

New Poster

 • 

10 Messages

14 hours ago

Out of curiosity, do you happen to be in the seattle area? I've been having similar-ish issues with ranging timeouts leading to high packet loss which reports as a warning in my unifi dream machine pro as well. Its definitely not my equipment as neighbors have reported similar issues

forum icon

New to the Community?

Start Here