Menu
Reply
Highlighted
  • 2
  • 0
  • 0
MidzAce
Joining in
201 Views
Message 1 of 4
Flag for a moderator

Super Hub 3 Crap :(

We recently upgraded to vivid 300.. all was working well with download and upload speeds. But my superhub keeps flashing green at early hours of the morning.. wifi logo and the arrows logo..

And it also slows down in peak times... why ? Especially when there supposed to be no traffic managment on our line...

Sort it out...
0 Kudos
Reply
  • 10.82K
  • 308
  • 631
Forum Team
Forum Team
152 Views
Message 2 of 4
Flag for a moderator

Re: Super Hub 3 Crap :(

Hi MidzAce,

 

Welcome to the community and thanks for posting.

 

Sorry to read you are having an issue with your broadband connection.

 

Looking at your connection, the line and hub have come back as fine. The are no faults reported and the traffic on the network is running low, which is good.

 

With the disconnection you mentioned (flashing lights), can you post the network log from the router settings for us to check over please? To do this type in 192.168.0.1 in the address bar, no need to sign in and click into Check router status. Within here you will have network log and you can copy and paste this information.

 

What speeds do you achieve during peak hours? Can you complete a speed test through a wired connection please?

 

Hope to hear from you soon

Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
  • 2
  • 0
  • 0
MidzAce
Joining in
117 Views
Message 3 of 4
Flag for a moderator

Re: Super Hub 3 Crap :(

Heres the Problem we had ! Router would not lock onto network.. All is fine now. apparently the area had a problem..

were now running at 300mb download and 20mb upload, at 9pm at night

Date And Time Error Number Event Description

2017-08-31 10:56:20.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-08-31 11:01:12.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-08-31 11:01:14.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-08-31 15:37:37.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-01 01:32:07.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-01 01:32:55.0082000400Received 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.0;
2017-09-01 01:33:42.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:24:47.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:24:47.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:24:47.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:24:48.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:24:52.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:25:05.0082000400Received 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.0;
2017-09-02 02:25:52.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:25:52.0084020300MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:26:05.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:27:25.0068000100DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-02 02:28:54.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-05 14:20:01.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-09-06 13:12:00.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 9.96K
  • 291
  • 624
Forum Team
Forum Team
88 Views
Message 4 of 4
Flag for a moderator

Re: Super Hub 3 Crap :(

Hi MidzAce,

Thanks for the update Smiley Happy

Good to hear this has since been resolved!

Let us know if we can help with anything else.

Take care.

Heather_J

Tech fan? Have you read our Digital life blog yet? Check it out


0 Kudos
Reply