Atom restart failure
Hi hub 3, I keep getting frequent disconnects which aligns to green WiFi light flashing. Running the test I get "intermittent issues reported" but then they resolve. looking at logs I have a lot of these around the time of the disconnections; "NOTICE ATOM is restarted due to Kernel/oops panic as part of Self Healing Mechanism" What is the next step? A replacement or router upgrade? I'm on a 350mb service. Thanks
TV losing connection since upgrading to 360 service
So I accepted the upgrade of my TV service too the 360 box. Since then wherever I try to watch streaming TV services, the WiFi connection drops out wherever the adverts come on! I'm thinking the issue is the router that can't cope.. The WiFi signal around the house is good(I have Tenda mesh system) Also the TV confirmed that it's connected to the WiFi but the connection drops out intermittently. I have also noticed VPN drops out when I'm working from home. Can someone check my router? I have the super hub 3 i think it's called.i also have 500mb service and only help 100 mb died downstairs....(But that's not the problem) Can't someone help... Do I need a newer router with the 360 TV service?Virgin Media Area Outage loop - N11 London
I’m at my wits’ end with Virgin Media. For over two months (since 31st May 2025), my broadband has been cutting out regularly. Every time I call or try to book an engineer, I get the same answer: They give a repair date, then either “fix” it for a day or two before the same fault pops up again — sometimes under a new fault ID — and the loop starts over. I went through my text alerts from Virgin and found a ridiculous chain of fault updates. Here’s the pattern just for this summer (those are only the alerts one, there were more in between those): 31 May – 12 June: Fault F011810225 — multiple repair date pushes, “engineer on the way,” “engineer on site,” then “issue fixed.” 24–25 June: Fault F011877105 — same story, marked as fixed. 21 July-25 July: Fault F011910493 . 25 July-31 July: Still issues and an operator ordered a replacement modem which did not solve the problem 3 August: Booked an engineer to fix this issue but this got cancelled for the area fault updated status 3–15 August: Fault F011937562 — constant shifting repair dates (5th, 6th, 8th, 13th, 15th), marked fixed… 15 August (Ongoing): The status has been (Fix( reset but there is intermitting issue when I check the website and I am sure it will re-loop Each “fix” lasts a couple of days at most before it’s back to square one. I’ve even had a technician appointment booked, then cancelled because it was supposedly “a network issue.” This has been going on for over 10 weeks now. I can’t get a proper engineer visit to my property. The “area fault” excuse keeps resetting the clock. Compensation is unclear unless I push for it. I cannot terminate the contract without paying for the exit fee Has anyone else had Virgin keep re-flagging the same problem as “new” to avoid escalation? How did you get them to actually fix the infrastructure, or at least give you consistent service? I’m considering filing a formal complaint and escalating to CISAS, but wanted to see if others have broken out of this loop before.Red light on hub reported and VM cancel technician
I have read elsewhere on this forum that red lights on hub 3 should not be ignored. I have had a solid red light for several weeks now. During this time I have checked the cables mulitple times, done multiple power cycles and two pinhole resets... still solid red. I explained this to a chat bot, then to person on the vm chat support, who eventually booked a technician visit for tomorrow. Then this morning i get an email and text saying the visit has been cancelled because the issue as been fixed. Email explains that they know it is fixed because they have been monitoring my account usage. Well... at no point did i say that i had no internet... so the fact i am using it does not mean my issue is fixed. And the light is still red. Others on here have said the solution is normally a replacement hub. Any advice on how to get this?Internet randomly dropping out since service outage.
We had some internet and TV problems last week due to a service outage in our area. On Wednesday the 20th I received a text message saying that the problem was fixed and that everything was up and running. Since then we have had nothing but problems with our internet dropping in and out randomly sometimes for hours at a time, sometimes coming on for 5 minutes and then dropping out again. I have checked all our cables are connected properly. I have reset the Hub 3 multiple times. I have removed all the ethernet cables that were connected to our Hub 3. I have also reset the Hub 3 to the factory settings. Nothing has worked. Usually the hub 3 shows a solid green light at the bottom, the up/down arrows flash green and the WIFI symbol stays solid green. Other times the bottom light flashes green, the up/down arrows aren't lit and the WIFI symbol stays green. It can switch back and forth between this light show for hours or sometimes just 10 minutes. We've been trying to keep track of the rough up and down time of the internet connection. This is from Monday 26th August. Off first thing in the morning. ON 10:18AM OFF 11:20AM ON 11:36AM OFF 12:20PM ON 12:40PM OFF 12:58PM ON 1:05PM OFF 1:24PM ON 1:55PM OFF 4:57PM ON 6:00PM OFF 6:10PM ON 6:14PM OFF 7:49PM ON 7:57PM OFF 8:01PM ON 9:09PM OFF 11PM Every day before Monday is like this on and off randomly all day. I did login to the router a few times after the internet had come back on and managed to get these from the logs: 25/08/2025 13:34:50 critical No Ranging Response received - T3 time-out;CM-MAC=18::b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:34:19 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18::b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:32:59 critical No Ranging Response received - T3 time-out;CM-MAC=18:3b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:32:56 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=1;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:31:40 critical No Ranging Response received - T3 time-out;CM-MAC=b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:31:39 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:29:56 critical No Ranging Response received - T3 time-out;CM-MAC=1:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:29:55 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:28:18 critical No Ranging Response received - T3 time-out;CM-MAC=18a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:28:16 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:27:14 critical No Ranging Response received - T3 time-out;CM-MAC=18:2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:25:37 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=18:35a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:23:21 critical No Ranging Response received - T3 time-out;CM-MAC=18a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:23:12 Warning! RCS Partial Service;CM-MAC=1:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:23:12 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=18:32;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:23:5 Warning! RCS Partial Service;CM-MAC=18:7:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:23:4 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=18:35:d1:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 13:00:28 Warning! RCS Partial Service;CM-MAC=182;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:11:56 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=1b;CMTS-MAC=04:;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:11:14 Warning! RCS Partial Service;CM-MAC=18b;CMTS-MAC=042;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:11:6 critical No Ranging Response received - T3 time-out;CM-MAC=8:ab;CMTS-MAC=04;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:10:46 Warning! RCS Partial Service;CM-MAC=18:ab;CMTS-MAC=01a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:09:40 critical No Ranging Response received - T3 time-out;CM-MAC=18:ab;CMTS-MAC=042;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:09:37 Warning! Lost MDD Timeout;CM-MAC=18:ab;CMTS-MAC=04:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:09:33 Warning! RCS Partial Service;CM-MAC=1b;CMTS-MAC=7:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:09:32 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=18:35:d:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 18:09:30 Warning! RCS Partial Service;CM-MAC=18;CMTS-MAC=04::b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:54:55 critical No Ranging Response received - T3 time-out;CM-MAC=18:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:54:52 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18::b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:53:14 critical No Ranging Response received - T3 time-out;CM-MAC=18b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:53:13 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:51:47 critical No Ranging Response received - T3 time-out;CM-MAC=18:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:51:45 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=181a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:50:35 critical No Ranging Response received - T3 time-out;CM-MAC=18c7:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:50:33 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:3:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:49:1 critical No Ranging Response received - T3 time-out;CM-MAC=18:7:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 17:48:29 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:35a:b2;CM-QOS=1.1;CM-VER=3.0; 01/01/1970 00:05:49 critical No Ranging Response received - T3 time-out;CM-MAC=18:32;CM-QOS=1.1;CM-VER=3.0; 01/01/1970 00:05:48 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:3a:b2;CM-QOS=1.1;CM-VER=3.0; 01/01/1970 00:04:46 critical No Ranging Response received - T3 time-out;CM-MAC=18:3:1a:b2;CM-QOS=1.1;CM-VER=3.0; 01/01/1970 00:04:44 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:352;CM-QOS=1.1;CM-VER=3.0; 01/01/1970 00:03:14 critical No Ranging Response received - T3 time-out;CM-MAC=1b2;CM-QOS=1.1;CM-VER=3.0; 01/01/1970 00:03:13 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:1a:b2;CM-QOS=1.1;CM-VER=3.0; 01/01/1970 00:01:43 critical No Ranging Response received - T3 time-out;CM-MAC=18:2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:59:23 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:32;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:57:35 critical No Ranging Response received - T3 time-out;CM-MAC=c7:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:57:33 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:3M-QOS=1.1;CM-VER=3.0; 25/08/2025 20:56:1 critical No Ranging Response received - T3 time-out;CM-MAC=18:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:55:58 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=15 20:54:27 critical No Ranging Response received - T3 time-out;CM-MAC=18:a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:54:24 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:52:29 critical No Ranging Response received - T3 time-out;CM-MAC=18CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:52:27 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=12;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:50:32 critical No Ranging Response received - T3 time-out;CM-MAC=18:2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:49:59 Warning! B-INIT-RNG Failure - Retries exceeded;CM-MAC=18:35:c7:1a:b2;CM-QOS=1.1;CM-VER=3.0; 25/08/2025 20:48:19 critical No Ranging Response received - T3 time-out;CM-MAC=18:3b2;CM-QOS=1.1;CM-VER=3.0; I'm hoping someone knows what the hub was trying to do and failing. And why at one point the Hub 3 thought it was 01/01/1970. Though I'd try here first before ringing as it's a lot easier to post some of the information than explaining over the phone. It's also hard to get time to ring during the working week. I've tried to find as much info as I can get but if there is anything else that would be helpful just let me know and I'll try to get it. Any help would be great as I've been customer since the Telewest days and never really had many problems with any of our services. Posting this using my phone as a WIFI hotspot as the Hub3 currently has a solid green bottom light, a flashing green up/down light and a soild green WIFI symbol. Thanks. [Mod - MACs removed for security]Factory Resetting of Hub3
Hi I have just swapped out my hub3 and successfully installed a hub5. Because I was concerned I might have issues, I deliberately did not factory reset my hub3 before disconnecting, just in case I had problems with the hub5 install and needed to roll back. I have since powered up my old hub3 and without connecting it back up have simply pressed the reset button for 30 secs. It then appeared to go through a restart and what could be a reset sequence but instead of eventually showing a solid white light (which I’ve read elsewhere is what happens at the end of the reset) the green WiFi light and light at bottom flash green…. I left it for over an hour and it continues to flash green - not a solid white light. Presumeably it’s flashing green because it can’t find any network (because I’ve not connected it back up). My question is: How can I be sure the factory reset has been successful? I don’t want to send it back to Virgin before I’ve removed my personal settings/device connection details etc… I’ve not attempted swapping it back in as I don’t want to mess up my hub5 activation in any way. Thanks in advance for any info you can give.