HI,
I'm having a similar problem with VM 100meg fibre BB. I had SSE FTTc ADSL previously (which was great at 38meg), but virgin recently dug up the roads (GL12 area) and offered a great introductory offer for 50 & 100meg. With SEE and VM I used the native modems in bridge mode (i.e. wifi router disabled)
I use an apple network (Time Capulse, 2 x airport extreme & 2 x airport express) around the house as we have very thick (stone) walls - it worked great with SSE, but streaming (iplayer, Netflix) and gaming (xbox one) is rubbish and keeps freezing & dropping out with VM. Even internet radio through an Amazon Echo drops out!
Doing speedtests on different devices, I frequently clock 110meg download, however I've also had it as low as 1.5meg.
I've called VM many times. To their credit they have sent 3 engineers around to try to resolve the problem (two of which has witness the poor streaming). They've replaced the VM router and I'm now just running that with my apple network off (still same streaming issues, please see: https://www.thinkbroadband.com/broadband/monitoring/... ). I've also purchased Net Uptime Monitor which longs dropouts (although you have to leave you PC on all the time). VM told me they will monitor my connection (through Think broadband), and if they can't fix the problem I 'may' be allowed to end the contract without further fees.
I really do hope they fix the issue, because although it's incredibly frustrating having the broadband drop out all the time, credit to VM in terms of trying to do something proactive and positive about the issue (I had expected to be fobbed off about 'poor wifi' blah, blah blah, which they didn't do).
I would be interested to hear if anyone else has experienced similar streaming issues.
I hope your Sky connection gets sorted. I know the tech is different, but if I do get a resolution, I'll post it as it may be of use. Good luck!

Its been up and down again this morning so I've reconnected the Sky router, cleared logs and will see what is in it when I get back in as I've had to head in to an office to get some work done. Sky are now quoting 19th December for an engineer to come out, so I'll see what the logs show tonight before deciding the next move.

I totally get these places have scripts to work through at a first line level, but its the default position of "you're doing it wrong" which gets a bit tiresome.

Sounds like you are doing it all wrong. What equipment were you using instead of the sky router?

When you have issues can you get the stats I asked for - will help all massively.

From the netgear. Connection has just dropped.

For some reason this time, the internet status light on the netgear for the dsl link is still white, so isn�t showing as being down, even though in the admin interface it�s showing as down.

Stats and log file info below.


System Up Time 05:58:59
Port Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN DHCP Client 13815887 19789499 0 173095 124990 05:57:05
LAN1 1000M/Full 23059963 16794080 0 414268 92923 05:58:12
LAN2 1000M/Full
LAN3 100M/Full
LAN4 100M/Full
WLAN b/g/n 600M 0 0 0 0 0 05:57:39
WLAN a/n/ac 1300M 1804765 1570708 0 88374 35077 05:57:35

VDSL Link Downstream Upstream
Link Rate. 31488 Kbps 8491 Kbps
Line Attenuation D0( 21.7) D1( 59.3) D2( 88.6) dB U0( 4.4) U1( 47.8) U2( 66.1) U3(N/A) U4(N/A) dB
Noise Margin D0( 5.4) D1( 5.4) D2(N/A) dB U0( 7.3) U1( 6.0) U2(N/A) U3(N/A) U4(N/A) dB
VDSL2 Profile Profile 17a


admin login] from source 192.168.0.11 Tuesday, December 12,2017 21:22:29
[DHCP IP: (192.168.0.11)] to MAC address DC:A4:CA:81:5E:BF Tuesday, December 12,2017 21:22:20
[DHCP IP: (192.168.0.25)] to MAC address 8C:70:5A:49:ED:68 Tuesday, December 12,2017 21:22:04
[DHCP IP: (192.168.0.25)] to MAC address 8C:70:5A:49:ED:68 Tuesday, December 12,2017 21:12:16
[admin login] from source 192.168.0.11 Tuesday, December 12,2017 21:11:43
[DHCP IP: (192.168.0.12)] to MAC address C8:69:CD:04:47:F2 Tuesday, December 12,2017 21:10:56
[DHCP IP: (192.168.0.12)] to MAC address C8:69:CD:04:47:F2 Tuesday, December 12,2017 21:09:45
[DHCP IP: (192.168.0.12)] to MAC address C8:69:CD:04:47:F2 Tuesday, December 12,2017 21:08:34
[DHCP IP: (192.168.0.12)] to MAC address C8:69:CD:04:47:F2 Tuesday, December 12,2017 21:07:23
[DHCP IP: (192.168.0.4)] to MAC address 40:98:AD:99:76:A6 Tuesday, December 12,2017 21:04:47
[DHCP IP: (192.168.0.11)] to MAC address DC:A4:CA:81:5E:BF Tuesday, December 12,2017 21:03:12
[Memory log total:227368KB used:127172KB free:100196KB] Tuesday, December 12,2017 21:01:00
[DoS attack: ACK Scan] from source: 216.58.206.67:443 Tuesday

Edited by mike_adams (Tue 12-Dec-17 21:34:01)

And from the Sky router....

System Up Time: 00:16:42
Port Status TxPkts RxPkts Collision Pkts Tx b/s Rx b/s Up Time
WAN Down 0 0 0 0 0 00:00:00
LAN Down 0 0 0 0 0 00:00:00
WLAN (2.4 GHz) Up 5301 0 0 13758 0 00:15:09
WLAN (5 GHz) Up 32210 34829 0 206272 27222 00:15:10
PLC Disable 0 0 0 0 0 00:00:00
Broadband Link Downstream Upstream
Connection Speed 34745 kbps 7845 kbps
Line Attenuation 27.7 dB 0.0 dB
Noise Margin 5.9 dB 6.6 dB


Connection Time
Connecting to ServerConnecting
Negotiation---
AuthenticationAUTO

Both show the line as synced, interesting the sky router is syncing faster than the Netgear.
Neither are showing you as without any sync...

The Sky router is displaying that it's trying to get an IP, this is common with Sky though when you switch routers, can take some time for a new MAC and device to be allowed onto the network.

Can you keep using the Sky router, just because it's the one I have so easier to diagnose:

If you head here: http://192.168.0.1/sky_st_poe.html - I am interested in the 2 fields in bold. I am expecting your connection time to be zero and connecting to server: to not be "connected"

Connection Status Close
Connection Time06:36:27
Connecting to ServerConnected
NegotiationMER
AuthenticationAUTO

EDIT: I wonder if your issues with the Sky Q router are just due to the Load Balancing, basically no device can saturate the internet speed alone, so it's common to get less on a speedtest, but if you run it on multiple devices it would saturate the link, just wouldn't on the one device. Overall it gives a better experience over multiple devices e.g. you generally don't see lag on any device vs 1 device getting everything and others suffering. For the Sky Q system a speedtest is not the best measure.

Edited by ukhardy07 (Tue 12-Dec-17 23:14:21)

Yes, that's exactly what those two fields show.

Sky were looking to get a BT engineer out, but looking like 10 days leadtime and they�re still saying chances are it�s something in the house setup. I�m going to cancel and go back to BT, the kicker being if I do this, Sky won�t book an Openreach engineer in the interim, but they way they�ve handled this has been shocking so I�ll just have to put up with the lack of service and deal with BT once I�ve switched back.

In reply to a post by mike_adams:

but they way they�ve handled this has been shocking

I can't see how you came to that conclusion.

They asked you to use the Sky router but you didn't, you used a Netgear.
They asked you to send photos of your master socket to show you had done their recommended fault finding so you wouldn't get charged £130, but you didn't.

You're probably carrying a line fault back to BT but good luck if you aren't because getting it fixed by BT could be a nightmare.