Forum Discussion

metalmatt's avatar
metalmatt
Superfast
2 years ago
Solved

Internet keeps dropping out

For the last week my Internet has been dropping off for 30 seconds then it comes back on again. I have a hub 5 and keep getting 16 consecutive T3 timeouts plus US profile assignment change. I have had loads of these errors today. Can someone look onto this please? Thanks. 

  • Great to hear this metalmatt 

    If you believe the issue to be resolved you can mark the thread as resolved by clicking the helpful answer given and this will show anyone else having issue that an answer was given and direct them to the post, alternatively you can just like or 'kudos' the post if it helped you. 

    Please let us know if you are having any further issues or have any questions at all. We'll be here to help on the community forums if needed :). 
     

  • Had the hub go off 2.35 in the morning not sure why. Here are the stats:

    04-06-2024 02:35:37 notice REGISTRATION COMPLETE - Waiting for Operational status
    04-06-2024 02:35:33 notice US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-06-2024 02:35:28 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-06-2024 02:35:25 notice TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-06-2024 02:35:22 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    04-06-2024 02:35:20 notice Honoring MDD; IP provisioning mode = IPv4
    04-06-2024 02:35:01 critical Cable Modem Reboot because of - unknown
    04-06-2024 02:35:01 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    • metalmatt's avatar
      metalmatt
      Superfast

      Same thing happened again this morning at 02:04am: Interesting error: 05-06-2024 02:04:37 critical Cable Modem Reboot because of - unknown. This one is a bit vague.

      05-06-2024 02:05:12 notice REGISTRATION COMPLETE - Waiting for Operational status
      05-06-2024 02:05:08 notice US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-06-2024 02:05:03 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-06-2024 02:04:59 notice TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-06-2024 02:04:57 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
      05-06-2024 02:04:55 notice Honoring MDD; IP provisioning mode = IPv4
      05-06-2024 02:04:37 critical Cable Modem Reboot because of - unknown
      05-06-2024 02:04:37 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1

      • Alex_RM's avatar
        Alex_RM
        Forum Team

        Thanks metalmatt,

        So I can take a closer look at things I've popped you over a private message.

        Alex_Rm

  • I have now reset my hub 5 I will monitor this for the next few days 🙂 

  • Had an engineer visit today, Glenn was absolutely super! he replaced the plug on the back of my hub and fitted an equalizer, adjusted all the levels, checked the wire. I will see how it goes.... Thanks again.

  • Since Sunday I have been getting some odd read outs. I'm not sure if the broadband stopped working as I was not in my house at the time. Since the Engineer last visit 2 weeks ago he checked everything out, the Hub 5, cabinet outside, and wires everything was perfect. The hub 5 seems like it reboots every morning around 2.37am for unknown reason in the logs. Not sure what the issue is really, apart from that broadband has been OK. Here is some of my log:

    26-06-2024 14:49:19 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-06-2024 06:34:25 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-06-2024 02:37:49 notice REGISTRATION COMPLETE - Waiting for Operational status
    26-06-2024 02:37:45 notice US profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-06-2024 02:37:39 notice DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-06-2024 02:37:36 notice TLV-11 - unrecognized OID;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-06-2024 02:37:33 warning DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-06-2024 02:37:31 notice Honoring MDD; IP provisioning mode = IPv4
    26-06-2024 02:37:12 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    26-06-2024 02:37:11 critical Cable Modem Reboot because of - unknown
    25-06-2024 02:38:04 critical Cable Modem Reboot because of - unknown
    25-06-2024 02:38:04 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:56:04 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:56:04 critical 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:54:56 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:54:03 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:54:03 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:53:42 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:53:33 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:26:37 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:26:10 critical SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:53 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:34 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:34 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:31 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:30 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:30 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:16 critical No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:16 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:15 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:15 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
    23-06-2024 15:25:08 critical Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;

    • Megan_L's avatar
      Megan_L
      Forum Team

      Hi MetalMatt, 

      Thanks for posting on our Community Forums!

      We've checked your services on our side and we've been unable to find any issues at all with your connection or Hub channels/specs. 

      Due to this we wouldn't worry to much about what you've mentioned, unless your connection does go downhill. 

      Keep us updated 🙂

      Thanks,

      Meg

       

      • metalmatt's avatar
        metalmatt
        Superfast

        Cheers yeah everything is fine tbh thanks for checking 🙂 

  • Mine is the same virgin keep sending engineers out and have said its a network issue but the network team won't come it's so frustrating have you had you problem sorted?

    • Ashleigh_C's avatar
      Ashleigh_C
      Forum Team

      Hi there Foxyfox8511 

      Thank you so much for your post and welcome to the community forums, it's great to have you here. 

      I can see that you have created your own post referencing the issues faced, an agent will respond to you as soon as possible where we will investigate this further for you there to avid confusion.

      Thank you.