Sky fibre stats

Just looking at my stats for my connection and was wondering if anyone could tell me if this looks ok?


Broadband Link Downstream Upstream
Connection Speed 27400 kbps 7079 kbps
Line Attenuation 26.4 dB 0.0 dB
Noise Margin 11.5 dB 6.6 dB


I have no idea where my cabinet is but I know when I first got it installed here for the first 12 months I had 34mb and it slowly dropped to what it is now.


Any advice appreciated or does everything look ok?


Many thanks

Your cabinet, based on your downstream attenuation is a fair way away from your house.

The SNR shows that there is still more speed to be squeezed out of the service.

try rebooting your sky hub and then share your stats again, your noise margin is nearly double what it should, once you reset it should reduce to 6.4 and you should gain some speed

Broadband Link Downstream Upstream
Connection Speed 27400 kbps 7089 kbps
Line Attenuation 26.4 dB 0.0 dB
Noise Margin 11.8 dB 6.6 dB

After a restart

Your line is banded at 27.4meg. Have you had a dropping connection problem recently?

By rebooting the router you've just started the DLM timer again so it's likely be a few weeks yet before your connection speed increases.

Edited by deleted (Tue 05-Apr-16 23:07:04)

Yes. The internet would drop out randomly and I would have to restart the Openreach Modem and Sky Hub to get it back on. I spoke to Sky who sent out the black hub which eliminates the Openreach modem.

You need to leave it connected without any disruptions or disconnections.

As I've said though it could take weeks due to how DLM operates after a banding is applied. When the banding is released you should get about an extra 8-10meg with the associated noise margin reduction.

Well I was only restarting it before as the connection had dropped and this was the only way to sort it.

Can Sky do anything regards to DLM or is it automatic?

Could they manually reset it themselves so it gives me the best speed?

Btw thanks to all that have replied and helped me out.

No manual resets, so a case of wait it out

Fair enough.

Is there anyway to find out where my cabinet is? I know of the BT checker but that just gives me the cab number and not the location or distance.

Cab number and exchange and someone will by magic find it on street view

Exchange is Acocks green and the cab number is 60

Cab 60 with copper PCP and a smaller fibre twin https://www.google.co.uk/maps/@52.4353264,-1.8242871...

Here you go

How do you find out?

It's magic

Nah, simply get the estimated postcode for the cabinet from Codelook and then "walk" the streets with google maps. Cabinets are USUALLY on or close to corners of street junctions, but not always.

Ooh I like that site. Going to have a play now with the site before you ask.

Thank youy

For some reason Sky told Openreach there was a fault on my line. Just had openreach here.

Told him about the drop outs and he did a few tests. Had to pop to my cabinet and reset the circuit as his equipment would not connect through my socket. After the reset it connected fine.

He said my line is 650m. Thats from my socket to the cab and its 4.1km to the exchange.

Anyway this is my stats now

Broadband Link Downstream Upstream
Connection Speed 35469 kbps 7295 kbps
Line Attenuation 26.4 dB 0.0 dB
Noise Margin 6.1 dB 6.6 dB

It may change but lets see how it goes I suppose.

http://www.speedtest.net/my-result/5232780179

In reply to a post by Skyfibreuser:

For some reason Sky told Openreach there was a fault on my line.

That's because there was one. The Openreach engineer should have fixed the fault and then reset the DLM. If the fault wasn't fixed, your speeds will drop again.

That's because there was one.

I'm afraid to say that's not always the case. CP's will test and test and test again until they manage to record the one test that 'comes back with an odd result', this way they can pass the fault to Openreach. You turn up as the engineer and it tests OK before, during, and after ....... It's all part of the 'game' that gets played these days.

I hasten to add that this may not be the case in this instance but ....

In reply to a post by Zarjaz:

That's because there was one.

I'm afraid to say that's not always the case. CP's will test and test and test again until they manage to record the one test that 'comes back with an odd result',

Is that not a fault then? Surely they are using Openreach's tools?

Is that not a fault then? Surely they are using Openreach's tools?

Sometimes, if you repeatedly test a line/service enough it will throw the odd 'duff' result using Openreach's test tools.

That's just the way it goes.

That just sounds like a intermittent fault, rather than a conspiracy.