Apparent Congestion, Hunslet MYHLT, FTTC

[#1]

Hi dowdican and welcome to the forums - great to have you on board
If you could also raise a fault at http://faults.plus.net and I'll see if I can get them both tied closely together.

[#2]

Please see attached.

[#3]

Fault number is 83428492
Download speedachieved during the test was - 61 Mbps
For your connection, the acceptable range of speedsis 61.95 Mbps-77.44 Mbps .
Additional Information:
IP Profile for your line is - 77.44 Mbps
2. Upstream Test: -provides background information.
Upload Speed
8.15 Mbps

0 Mbps 20 Mbps
Max Achievable Speed
Upload speed achieved during the test was - 8.15Mbps
Additional Information:
Upstream Rate IP profile on your line is - 20 Mbps

[#4]

Thanks for all your information.
We think there might be a problem with the VLAN - Dan is heading this up with both tickets

[#5]

Thanks Chris, I take it you're referring to the VLAN between cabinet and the OLT/L2S in the exchange, as you couldn't see widespread issues on Hunslet as you'd expect if the problem were the Cablelink or onwards SVLAN to the BTW network?
Sorry Dowdican for the acronym soup

[#6]

I assume that Dan is referring to the VLAN between cabinet and the OLT/L2S as you say.
This requires further investigation with our suppliers, I believe that's what Dan is doing at the moment.

[#7]

Thank you.
Was disconnected during the testing I guess; have connected to a new gateway, pcl-ag01 where previous was pcl-ag03, and seem to be taking a different route through the BT Wholesale network:

Will see if that makes any difference.

[#8]

Okay.

Quote

I have tested your connection and we believe that it is related to an issue on the backhaul network connecting a few exchanges around the Leeds area. This information has now been passed to our suppliers for further investigation.

I hope this is the issue. Certainly Bingley seems in way worse shape than we are, and this issue has been evident since January according to my graphs so it's manifesting itself in some weird ways.
January 19th:

[#9]

Confirmed as not being related to the Bingley issues.
Will let this thread die its death as this is being investigated elsewhere.

[#10]

Wanted to update.
This issue still seems to be ongoing despite capacity upgrades.

[#11]

Has this been a daily thing?
There's also further maintenance on your exchange this week(16th) for the node you're connected too that may help.