In reply to a post by uno:

BT have committed to a date in January for a new 10Gb link to solve this but suspect it might be related.

Great info ... Thanks Matt.
I wonder why Zen arent able to tell us information like this. Beginning to think I've made the wrong choice of ISP!

Same area as we're seeing this issue.

Update from BT on 22nd December was:

I have spoken to the Operations team, and also the Tech Services team this morning, and they are not able to make any further improvement to the traffic load at Aboyne. So unfortunately we will need to wait until mid-January when the new 10Gig backhaul into Aboyne will be completed.

Matt

In reply to a post by craski:

I wonder why Zen aren't able to tell us information like this. Beginning to think I've made the wrong choice of ISP!

Zen do provide this info

In reference to status.zen.co.uk/broadband/:

Fault BT59810 29/12/2015 16:45 31/12/2015 04:00
01224 01236 01241 01259 01307 01309 01312 01313 01314 01315 01316 01324 01330 01337 01339 01349 01355 01356 01357 01358 01360 01361 01369 01382 01383 01389 01397 01412 01413 01414 01415 01416 01417 01418 01419 01434 01436 01463 01466 01467 01475 01501 01502 01505 01506 01555 01561 01569 01575 01578 01595 01620 01651 01661 01665 01667 01668 01674 01698 01721 01771 01779 01828 01830 01851 01855 01875 01888 01896 01899 01912 01968 01975 02476 02820 02821 02825 02827 02828 02829 02837 02840 02842 02843 02844 02866 02867 02868 02870 02871 02877 02879 02880 02882 02886 02890 02891 02892 02893 02894 02897

Zen Status

Edited by tommy45 (Thu 31-Dec-15 12:20:43)

Same here in north east, packet loss ,pings have doubled and I have ran on fast for years ,and now damn interleaving has been applied !!!
Exchange Code: NESLN

There's no way congested backhaul could cause interleaving to be applied, I suspect another issue there with the cabling to your house.

This isn't related to what you've posted though, or any moment in time outages.

This congestion has been going on for a while as you'll see from the other posters.

Matt

In reply to a post by uno:

This isn't related to what you've posted though, or any moment in time outages.

This congestion has been going on for a while as you'll see from the other posters.

Matt

Yes there is two issues at play or there was, Some customers have only started seeing this lag tsunami since the 29/12/15 and for those it maybe be sorted if their STD codes are on that list , as for the other issue that has been ongoing for a longer time, Matt is there not a BT number for that and details of which STD's are affected, or is that considered "commercially sensitive "info by BTW ?

Edited by tommy45 (Thu 31-Dec-15 13:42:59)

No, because it is not considered an outage which you'd get a BIR for.

It's not linked on the exchange either so when you raise a fault for an affected CLI, you get the "standard" returned fault stating no fault found/customer mis-operation and to book an engineer visit.

Only after you provide graphing and data showing this problem do they then reveal issues. There have been SVLAN changes to help which worked but now everything there appears to be suffering because BT have not provisioned sufficient capacity locally.

Matt

Yup, found that yesterday and that fault was showing as being opened and closed on 29th Dec.
It now appears to have been updated this morning to show fault closed at of 0400 on 31st which it previously didnt say.

I do hope that solves the problem we've seen over past 2 evenings with latency at >120ms and speeds at ~2Mb (on a line that syncs at 80/20) but I was having issues with my connection losing a lot of speed in evening before this latest fault to what looks like congestion and that appears to be related to what Matt was saying about BT's back haul capacity in parts of Scotland.

In reply to a post by uno:

No, because it is not considered an outage which you'd get a BIR for.

It's not linked on the exchange either so when you raise a fault for an affected CLI, you get the "standard" returned fault stating no fault found/customer mis-operation and to book an engineer visit.

Only after you provide graphing and data showing this problem do they then reveal issues. There have been SVLAN changes to help which worked but now everything there appears to be suffering because BT have not provisioned sufficient capacity locally.

Matt

Typical of BT They seem to like running things on the hot side especially SVLANS which is why they can shift you onto a different one and within a month the peak time capacity issues can return, because they are too highly contended imo,