Broadband Dropping Out Approx Every 24hrs

[pscraven]

Hi, I retained the same hub, and have tried moving the hub to the other side of the same room previously to no avail.  I only have a single master socket in the house, and no phones connected. I will try AM 612 Mhz and see if that identifies any noise. Thank you for the reply.

[pscraven]

Hi @kamen , Glad to know Im not the only one ;). Im in Warwick (CV35), so I guess that rules out the same switch/cabinet at least!  I hope you get a resolution, please post of you do. Thanks!

[kamen]

@pscraven here are my timings since I rejoined BT two weeks ago. It didn't drop on Sunday, but dropped the previous Sunday.

It seems that in both of our cases the problems started after a change - the cutoff in your case and a change of provider in mine. In your case the hub is the same, in my case I had the issue with the Sky hub and with the new BT one. We both have tried changing the location of the hub without any difference. We both had visits from an engineer without success.

I'm pretty sure it's not something in the house causing it as nothing has changed and nothing specific happens around noon. I'll do a few more tests to be even more certain and will give BT another call.

I'm surprised they can't monitor the line from their side, but maybe it will take more calls before we get to someone who really knows the network and can do proper investigation.

Time	Message
11:12:21	22 Feb. DSL Link Down: duration was 7096 seconds
11:06:28	21 Feb. DSL Link Down: duration was 85130 seconds
11:27:04	20 Feb. DSL Link Down: duration was 172815 seconds
11:26:14	18 Feb. DSL Link Down: duration was 86272 seconds
11:27:49	17 Feb. DSL Link Down: duration was 35203 seconds
01:40:20	17 Feb. DSL Link Down: duration was 48153 seconds
12:17:12	16 Feb. DSL Link Down: duration was 87237 seconds
12:02:40	15 Feb. DSL Link Down: duration was 12387 seconds
12:37:25	14 Feb. DSL Link Down: duration was 89460 seconds
11:45:52	13 Feb. DSL Link Down: duration was 81364 seconds
13:09:15	12 Feb. DSL Link Down: duration was 85841 seconds
13:18:00	11 Feb. DSL Link Down: duration was 93770 seconds
11:14:36	10 Feb. DSL Link Down: duration was 31169 seconds
02:34:29	10 Feb. DSL Link Down: duration was 3522 seconds
01:35:22	10 Feb. DSL Link Down: duration was 46081 seconds
12:46:43	09 Feb. DSL Link Down: duration was 88746 seconds
12:07:03	08 Feb. DSL Link Down: duration was 15124 seconds

[kamen]

@pscraven one other thing - are you on a full fibre connection to your house? I'm on the old copper cable to the house, presumably there is fibre to the cabinet

[pscraven]

Hi again, it’s interesting that the situation is almost identical. I am on Fibre 2 so fibre to the cabinet, copper to the house. I am trying to find out if my neighbours are also affected. I am considering if my situation could be the result of the fire alarm being changed which was around the same time as the BB came back online about 6th Jan, although I can’t see why I’m this would be the cause. The only other change I can think of is smart meters being commissioned. Again I can’t understand why although it may be a possibility I guess. Other than that nothing else has changed inside the house. I have an escalation case now with BT open.

[rbz5416]

Is the fire alarm connected to the phone line? Maybe it is trying to "phone home" daily to the manufacturer/installer, despite there being no service.

[pscraven]

No, totally separate to my house and not connected to the phone system. It’s part of a shared entrance only but I will investigate just in case. Thanks

[kamen]

hi @pscraven , any progress on your side?

I just called BT again and they booked another engineer to come on Thursday. Apparently a different type of engineer from the previous one, I think the guy on the call said 'cube engineer', but I may have misheard.

[pippincp]

All a Qube engineer can do is check your set up, totally useless in this situation.

[kamen]

The prediction was correct. The Qube engineer came, connected a laptop to the router, run some tests and said that everything was ok.

At least I showed him the router logs showing the drops and pressed him on next steps. He said he'll write in his report a suggestion to monitor the line for 48 hours to hopefully see these drops from their side.