Order posts by limited to posts

5 Aug
Details
5 May 22:22:42

TalkTalk is performing essential maintenance on its internal infrastructure. This work will happen in the early hours of the 8th May 2015. This work will mean that services may be lost for up to 1 hour between midnight and 6am. This is likely to affect the following exchanges:

  • FLAX BOURTON
  • REDCLIFFE
  • WEDMORE
  • Yatton
  • Didcot
  • CHURCHDOWN
  • Cheltenham
  • SHRIVENHAM
  • STRATTON ST MARGARET
  • Swindon
  • Blunsdon
  • Cirencester
  • CRICKLADE
  • HAYDON WICK
  • PURTON
  • BATHEASTON
  • BOX
  • BRADENSTOKE
  • Chippenham
  • CORSHAM
  • CHURCHILL
  • Clevedon
  • NAILSEA
  • WRINGTON
  • LONG ASHTON
  • PILL
  • Brimscombe
  • Dursley
  • NAILSWORTH
  • TETBURY
  • Calne
  • Devizes
  • HAWTHORN
  • Melksham
  • NORTH TROWBRIDGE
  • BANWELL
  • BLEADON
  • WINSCOMBE
  • Worle
  • Weston Super Mare
  • ABSON
  • Downend
  • FISHPONDS
  • SALTFORD
  • CHEW MAGNA
  • Midsomer Norton
  • Radstock
  • STRATTON-ON-FOSSE
  • TEMPLE CLOUD
  • TIMSBURY
  • STOKE BISHOP
  • West
  • Frome
  • MELLS
  • WARMINSTER
  • BRADFORD-ON-AVON
  • LIMPLEY STOKE
  • Trowbridge
  • Westbury
  • ALMONDSBURY
  • FILTON
  • HENBURY
  • AVONMOUTH
  • PILNING
  • Portishead
  • BEDMINSTER
  • BISHOPSWORTH
  • BITTON
  • KEYNSHAM
  • Kingswood
  • CHIPPING SODBURY
  • FALFIELD
  • WINTERBOURNE
  • WOTTON UNDER EDGE
  • FAIRFORD
  • LECHLADE
  • MALMESBURY
  • SOUTH CERNEY
  • TOOTHILL
  • WOOTTON BASSETT
  • COMBE DOWN
  • Kingsmead
  • Bristol North
  • WESTBURY-ON-TRYM
  • EASTON
  • EASTVILLE
  • South
  • WHITCHURCH
  • LAVINGTON
  • MARLBOROUGH
  • PEWSEY
  • WROUGHTON
  • WANBOROUGH
  • LULSGATE
  • Glastonbury
  • OAKHILL
  • Wells
  • BERKELEY
  • THORNBURY
We apologise for any inconvenience that these works may cause you
Planned start 5 Aug by TalkTalk

13 May 12:13:36
Details
5 May 10:21:17
BT have had trouble with this exchange (http://aastatus.net/2052) but we are now seeing evening congestion on TalkTalk connected lines. We have reported this and will update this post accordingly.
Update
5 May 12:38:47
TalkTalk have fixed a misconfiguration at their end. This should now be resolved. We'll check again tomorrow.
Update
7 May 08:55:48
Lines still seem to be congested, this is being looked in to by TalkTalk.
Update
13 May 12:13:36
Update from TT 'This should now properly be resolved. A faulty interface meant that we were running at 2/3 of capacity - only a few of your subscribers would have suffered last night hopefully but should now all be good.'
Started 5 May 10:00:00

4 May 21:52:34
Details
4 May 21:41:59
We are are seeing congestion on HORNDEAN and WATERLOOVILLE exchanges (Hampshire). This is usually noticeable in the evenings. This will be reported to BT, and we'll update this post with updates.
Started 4 May 21:38:34

14 May 15:42:00
Details
14 May 15:42:00

We are please to inform customers that we are changing the entry-level router that we supply to our customers. From next week we'll be shipping the ZyXEL VMG1312 by default instead of the Technicolor.

Since around 2012 we have been providing the Technicolor TG852, which was the first consumer level router to support IPv6. With the advent of wires-only FTTC and the need for a more flexible and easy to use router we have been looking for a replacement. The ZyXEL VMG1312 is able to do ADSL, FTTC and PPPoE and is flexible enough to be used on most of our lines. We have been working with ZyXEL over the past few months to iron out bugs that we have found. There are still some bugs to be fixed and these are detailed on our Support site. The biggest bug is the lack of 1500 byte MTU when running in bridge mode, however, ZyXEL expect to have this fixed soon and in the meantime FTTC installations will be installed with the Openreach modem.

More information about the router: https://support.aa.net.uk/Category:ZyXEL_VMG1312

Started 14 May 13:12:00

13 May 12:16:45
Details
26 Mar 09:53:31

Over the past couple of weeks we have seen FTTC lines drop and reconnect with in increase in latency of around 15ms. This is seen on the monitoring graphs as a thicker blue line.

Upon first glance it looks as if interleaving has been enabled, but a line test shows that this is not the case.

We've been in contact with BT and it does look like BT are rolling out a new profile on to their Huawei DSLAMs in the local green cabinets. It has been expected that BT would be rolling out this new profile, but we didn't expect such an increase in latency.

The profile adds 'Physical Retransmission (ReTX) technology (G.INP / ITU G.998.4)' which helps with spikes of electromagnetic interference and can make lines more stable.

We would hope to have control over the enabling and disabling of this profile, but we don't. Line profiles with FTTC is managed by BT Openreach and are tricky for us and even BT Wholesale to get adjusted.

We're still discussing this with BT and will update this post with news as we have it.

Update
26 Mar 09:55:29
Update
26 Mar 10:48:37
This has been escalated to the head of fibre deployment within BT Wholesale and we are expecting an update by the end of the day.
Update
26 Mar 11:12:08
Further information about G.INP:
  • http://www.ispreview.co.uk/index.php/2015/01/bt-enables-physical-retransmission-g-inp-fttc-broadband-lines.html
  • http://www.thinkbroadband.com/news/6789-impulse-noise-protection-rolling-out-on-openreach-vdsl2.html
  • http://forum.kitz.co.uk/index.php?topic=15099.0
...among others.
Update
27 Mar 16:46:22
BT have asked us for further information which we have provided to them, we don't expect an update now until Monday
Update
9 Apr 14:26:19
This is still ongoing with BT Wholesale and BT Openreach.
Update
16 Apr 15:58:53
This has been escalated to a very senior level within BT and we are expecting a proper update in the next few days.
Update
24 Apr 13:01:45
We have just received the below back from BT on this

Following communications from a small number of BTWholesale FTTC comms providers regarding Openreach’s implementation of Retransmission and the identification of some your customers who have seen increased latency on some lines for some applications since retransmission was applied. Over the last 4 weeks I have been pushing Openreach to investigate,

feedback and provide answers and options related to this issue. As a result attached is a copy of a briefing from Openreach; sent to their CPs today, on how RetX works and what may have caused this increase latency.

This info is being briefed to all BTWholesale customers via our briefing on Saturday morning 25/4/15 but as you have contacted me direct I’m sending this direct as well as providing ann opportunity to participate in a trial.

Openreach have also advise me this afternoon that they intend to run a trial next week (w/c 25/4/15) on a small set of lines; where devices aren’t retransmission compatible in the upstream to see if changing certain parameters removes the latency and maintains the other benefits of retransmission. The exact date lines will be trialled has yet to be confirmed.

However, they have asked if I have any end users who would like to be included in this trail. To that end if you have particular lines you’d like to participate in this trial please can you provide the DN for the service by 17:00 on Monday 28th April so I can get them included.

This is a trial of a solution and should improve latency performance but there is a risk that there may be changes to the headline rate.

Update
5 May 22:28:25
Update to Trial here: https://aastatus.net/2127
Started 26 Mar 09:00:00
Closed 13 May 12:16:45

12 May 13:41:47
Details
11 May 18:07:36
We have changed the way we apply minimum terms.

Instead of charging for all of the service to the end of the minimum term, we now charge an early termination fee for the period from the cease/migrate to the end of the term. This is a simple fee based on the tariff and line type. We are also scrapping the 30 day notice requirement.

Whilst the old system was simple, it did not fit OFCOM rules for the new migration system. We think the new system is equally simple, and saves customers money. As such the change has been introduced today.

More details here http://aa.net.uk/news-20150511-minterm.html

Started 11 May 18:00:00

23 Apr 2014 10:21:03
Details
01 Nov 2013 15:05:00
We have identified an issue that appears to be affecting some customers with FTTC modems. The issue is stupidly complex, and we are still trying to pin down the exact details. The symptoms appear to be that some packets are not passing correctly, some of the time.

Unfortunately one of the types of packet that refuses to pass correctly are FireBrick FB105 tunnel packets. This means customers relying on FB105 tunnels over FTTC are seeing issues.

The work around is to remove the ethernet lead to the modem and then reconnect it. This seems to fix the issue, at least until the next PPP restart. If you have remote access to a FireBrick, e.g. via WAN IP, and need to do this you can change the Ethernet port settings to force it to re-negotiate, and this has the same effect - this only works if directly connected to the FTTC modem as the fix does need the modem Ethernet to restart.

We are asking BT about this, and we are currently assuming this is a firmware issue on the BT FTTC modems.

We have confirmed that modems re-flashed with non-BT firmware do not have the same problem, though we don't usually recommend doing this as it is a BT modem and part of the service.

Update
04 Nov 2013 16:52:49
We have been working on getting more specific information regarding this, we hope to post an update tomorrow.
Update
05 Nov 2013 09:34:14
We have reproduced this problem by sending UDP packets using 'Scapy'. We are doing further testing today, and hope to write up a more detailed report about what we are seeing and what we have tested.
Update
05 Nov 2013 14:27:26
We have some quite good demonstrations of the problem now, and it looks like it will mess up most VPNs based on UDP. We can show how a whole range of UDP ports can be blacklisted by the modem somehow on the next PPP restart. It is crazy. We hope to post a little video of our testing shortly.
Update
05 Nov 2013 15:08:16
Here is an update/overview of the situation. (from http://revk.www.me.uk/2013/11/bt-huawei-fttc-modem-bug-breaking-vpns.html )

We have confirmed that the latest code in the BT FTTC modems appears to have a serious bug that is affecting almost anyone running any sort of VPN over FTTC.

Existing modems seem to be upgrading, presumably due to a roll out of new code in BT. An older modem that has not been on-line a while is fine. A re-flashed modem with non-BT firmware is fine. A working modem on the line for a while suddenly stopped working, presumably upgraded.

The bug appears to be that the modem manages to "blacklist" some UDP packets after a PPP restart.

If we send a number of UDP packets, using various UDP ports, then cause PPP to drop and reconnect, we then find that around 254 combinations of UDP IP/ports are now blacklisted. I.e. they no longer get sent on the line. Other packets are fine.

Sending 500 different packets, around 254 of them will not work again after the PPP restart. It is not actually the first or last 254 packets, some in the middle, but it seems to be 254 combinations. They work as much as you like before the PPP restart, and then never work after it.

We can send a batch of packets, wait 5 minutes, PPP restart, and still find that packets are now blacklisted. We have tried a wide range of ports, high and low, different src and dst ports, and so on - they are all affected.

The only way to "fix" it, is to disconnect the Ethernet port on the modem and reconnect. This does not even have to be long enough to drop PPP. Then it is fine until the next PPP restart. And yes, we have been running a load of scripts to systematically test this and reproduce the fault.

The problem is that a lot of VPNs use UDP and use the same set of ports for all of the packets, so if that combination is blacklisted by the modem the VPN stops after a PPP restart. The only way to fix it is manual intervention.

The modem is meant to be an Ethernet bridge. It should not know anything about PPP restarting or UDP packets and ports. It makes no sense that it would do this. We have tested swapping working and broken modems back and forth. We have tested with a variety of different equipment doing PPPoE and IP behind the modem.

BT are working on this, but it is a serious concern that this is being rolled out.
Update
12 Nov 2013 10:20:18
Work on this in still ongoing... We have tested this on a standard BT retail FTTC 'Infinity' line, and the problem cannot be reproduced. We suspect this is because when the PPP re-establishes a different IP address is allocated each time, and whatever is session tracking does not match the new connection.
Update
12 Nov 2013 11:08:17

Here is an update with some a more specific explanation as to what the problem we are seeing is:

On WBC FTTC, we can send a UDP packet inside the PPP and then drop the PPP a few seconds later. After the PPP re-establishes, UDP packets with the same source and destination IP and ports won't pass; they do not reach the LNS at the ISP.

Further to that, it's not just one src+dst IP and port tuple which is affected. We can send 254 UDP packets using different src+dest ports before we drop the PPP. After it comes back up, all 254 port combinations will fail. It is worth noting here that this cannot be reproduced on an FTTC service which allocates a dynamic IP which changes each time PPP re-established.

If we send more than 254 packets, only 254 will be broken and the others will work. It's not always the first 254 or last 254, the broken ones move around between tests.

So it sounds like the modem (or, less likely, something in the cab or exchange) is creating state table entries for packets it is passing which tie them to a particular PPP session, and then failing to flush the table when the PPP goes down.

This is a little crazy in the first place. It's a modem. It shouldn't even be aware that it's passing PPPoE frames, let along looking inside them to see that they are UDP.

This only happens when using an Openreach Huawei HG612 modem that we suspect has been recently remotely and automatically upgraded by Openreach in the past couple of months. Further - a HG612 modem with the 'unlocked' firmware does not have this problem. A HG612 modem that has probably not been automatically/remotely upgraded does not have this problem.

Side note: One theory is that the brokenness is actually happening in the street cab and not the modem. And that the new firmware in the modem which is triggering it has enabled 'link-state forwarding' on the modem's Ethernet interface.

Update
27 Nov 2013 10:09:42
This post has been a little quiet, but we are still working with BT/Openreach regarding this issue. We hope to have some more information to post in the next day or two.
Update
27 Nov 2013 10:10:13
We have also had reports from someone outside of AAISP reproducing this problem.
Update
27 Nov 2013 14:19:19
We have spent the morning with some nice chaps from Openreach and Huawei. We have demonstrated the problem and they were able to do traffic captures at various points on their side. Huawei HQ can now reproduce the problem and will investigate the problem further.
Update
28 Nov 2013 10:39:36
Adrian has posted about this on his blog: http://revk.www.me.uk/2013/11/bt-huawei-working-with-us.html
Update
13 Jan 2014 14:09:08
We are still chasing this with BT.
Update
03 Apr 2014 15:47:59
We have seen this affect SIP registrations (which use 5060 as the source and target)... Customers can contact us and we'll arrange a modem swap.
Update
23 Apr 2014 10:21:03
BT are in the process of testing an updated firmware for the modems with customers. Any customers affected by this can contact us and we can arrange a new modem to be sent out.
Update
7 May 22:56:52
Just a side note on this, we're seeing the same problem on the ZyXEL VMG1312 router which we are teting out and which uses the same chipset: info and updates here: https://support.aa.net.uk/VMG1312-Trial
Resolution BT are testing a fix in the lab and will deploy in due course, but this could take months. However, if any customers are adversely affected by this bug, please let us know and we can arrange for BT to send a replacement ECI modem instead of the Huawei modem. Thank you all for your patience.

--Update--
BT do have a new firmware that they are rolling out to the modems. So far it does seem to have fixed the fault and we have not heard of any other issues as of yet. If you do still have the issue, please reboot your modem, if the problem remains, please contact support@aa.net.uk and we will try and get the firmware rolled out to you.
Started 25 Oct 2013
Closed 23 Apr 2014 10:21:03

7 May 09:53:49
Details
09 Dec 2014 11:20:04
Some lines on the LOWER HOLLOWAY exchange are experiencing peak time packet loss. We have reported this to BT and they are investigating the issue.
Update
11 Dec 2014 10:46:42
BT have passed this to TSO for investigation. We are waiting for a further update.
Update
12 Dec 2014 14:23:56
BT's Tso are currently investigating the issue.
Update
16 Dec 2014 12:07:31
Other ISPs are seeing the same problem. The BT Capacity team are now looking in to this.
Update
17 Dec 2014 16:21:04
No update to report yet, we're still chasing BT...
Update
18 Dec 2014 11:09:46
The latest update from this morning is: "The BT capacity team have investigated and confirmed that the port is not being over utilized, tech services have been engaged and are currently investigating from their side."
Update
19 Dec 2014 15:47:47
BT are looking to move our affected circuits on to other ports.
Update
13 Jan 10:28:52
This is being escalated further with BT now, update to follow
Update
19 Jan 12:04:34
This has been raised as a new reference as the old one was closed. Update due by tomorrow AM
Update
20 Jan 12:07:53
BT will be checking this further this evening so we should have more of an update by tomorrow morning
Update
22 Jan 09:44:47
An update is due by the end of the day
Update
22 Jan 16:02:24
This has been escalated further with BT, update probably tomorrow now
Update
23 Jan 09:31:23
we are still waiting for a PEW to be relayed to us. BT will be chasing this for us later on in the day.
Update
26 Jan 09:46:03
BT are doing a 'test move' this evening where they will be moving a line onto another VLAN to see if that helps with the load, if that works then they will move the other affected lines onto this VLAN. Probably Wednesday night.
Update
26 Jan 10:37:45
there will be an SVLAN migration to resolve this issue on Wednesday 28th Jan.
Update
30 Jan 09:33:57
Network rearrangement is happening on Sunday so we will check again on Monday
Update
2 Feb 14:23:12
Network rearrangement was done at 2AM this morning, we will check for paclet loss and report back tomorrow.
Update
3 Feb 09:46:49
We are still seeing loss on a few lines - I am not at all happy that BT have not yet resolved this. A further escalation has been raised with BT and an update will follow shortly.
Update
4 Feb 10:39:03
Escalated futher with an update due at lunch time
Update
11 Feb 14:14:58
We are getting extremly irritated with BT on this one, it should not take this long to add extra capaity in the affected area. Rocket on it's way to them now ......
Update
24 Feb 12:59:54
escalated further with BT, update due by the end of the day.
Update
2 Mar 09:57:59
We only have a few customers left showing peak time packet loss and for now the fix will be to move them onto another MSAN, I am hoping this will be done in the next few days. We really have been pushing BT hard on this and other areas where we are seeing congestion. I am please that there are now only a handful of affected customers left.
Update
17 Mar 11:21:33
We have just put a boot up BT on this, update to follow.
Update
2 Apr 13:16:10
BT have still not fixed the fault so we have moved some of the affected circuits over to TalkTalk and I am pleased to say that we are not seieng loss on those lines. 100% this is a BT issue and I am struggling to understand why they have still not tracked the fault down.
Closed 7 May 09:53:49
Previously expected 1 Feb 09:34:04 (Last Estimated Resolution Time from AAISP)

7 May 09:52:18
Details
11 Mar 11:39:17
We are seeing some evening time congestion on all BT 21CN lines that connect through BRAS's 21CN-BRAS-RED1-MR-DH up to 21CN-BRAS-RED13-MR-DH I suspect one of the BT nodes is hitting limits some evenings as we don't see the higher latency every night. This has been reported into BT and we will update this past as soon as they respond back.
Update
11 Mar 11:44:06
Here is an example graph
Update
12 Mar 12:00:45
This has been escalated further to the BT networK guys and we can expect an update within the next few hours.
Update
17 Mar 15:41:18
Work was done on this overnight so I will check again tomorrow morming and post another update.
Update
18 Mar 11:38:25
The changes BT made over night have made a significant difference to the latency, still seeing it slightly higher than we would like so we will go back to then again.
Update
19 Mar 14:54:44
Unfortunately the latency has increased again so whatever BT did two nights ago has not really helped. We are chasing again now.
Update
23 Mar 14:07:53
BT have still not pinpointed the issue so it has been escalated further.
Update
27 Mar 13:03:38
Latency is hardly noticeable now but we are still chasing BT on sorting the actual issue, update will be mOnday now.
Update
30 Mar 10:04:14
BT have advised that they are aware of the congestion issue at Manchester, and the solution they have in place is to install some additional edge routers, they are already escalating on this to bring the date in early, currently the date is May. Obviously May is just not acceptable and we are doing all we can to get BT to bring this date forward.
Update
2 Apr 12:28:39
We have requested a further escalation within BT, the time scales they have given for a fix is just not acceptable.
Update
13 Apr 15:12:23
The last update from BT was 'is latency issue has been escalated to high level. BT TSO are currently working on a resolution and are hoping to move into the testing phase soon. We will keep you updated as we get more information' I am chasing for another update now.
Update
16 Apr 16:01:15
We are still chasing BT up on bringing the 'fix' forward. Hopefully we will have another response by the morning.
Update
21 Apr 13:25:21
The latest update from BT: We have identified a solution to the capacity issue identified and are looking to put in a solution this Friday night...
Update
24 Apr 15:25:51
BT have added more capacity on tehir network and last night the latency looked fine. We will review this again on Monday.
Started 11 Mar 01:35:37
Closed 7 May 09:52:18

29 Apr 15:23:27
Details
29 Apr 14:43:36
A third of our BT lines bliped - this looks to be an issue with routing on one of our LNSs in to BT.
Update
29 Apr 14:50:18
Many lines are failing to reconnect properly, we are investigating this.
Update
29 Apr 14:57:42
Lines are connecting successfully now
Update
29 Apr 15:23:27
The bulk of lines are back onlne. There are a small number of lines that are still failing to reconnect. These are being looked in to.
Update
29 Apr 15:36:54
The remain lines are reconnecting successfully now.
Resolution I wanted to try and explain more about what happened today, but it is kind of tricky without saying "Something crazy in the routing to/from BT".

We did, in fact make a change - something was not working with our test LNS and a customer needed to connect. We spotted that, for some unknown reason, the routing used a static route internally instead of one announced by BGP, for just one of the four LNSs, and that on top of that the static route was wrong, hence the test LNS not working via that LNS. It made no sense, and as all three other LNSs were configured sensibly we changed the "A" LNS to be the same, after all, this is clearly a config that just worked and was no problem, or so it seemed.

Things went flappy, but we could not see why. It looks like BGP in to BT was flapping, so people connected and disconnected rather a lot. We returned the config and things seemed to be fixed for most people, but not quite all. This made no sense. Some people are connecting and going on line, and then falling off line.

The "fix" to that was to change the endpoint LNS IP address used by BT to an alias on the same LNS. We have done this in the past where BT have had a faulty link in a LAG. We wonder if this issue was "lurking" and the problem we created showed it up. This shows that there was definitely an issue in BT somehow as the fix should not have made any difference otherwise.

What is extra special is that this looks like it has happened before - the logs suggest the bodge of a static route was set up in 2008, and I have this vague recollection of a mystery flappiness like this which was never solved.

Obviously I do apologise for this, and having corrected the out of data static route this should not need touching again, but damn strange.

Started 29 Apr 14:38:00
Closed 29 Apr 15:23:27
Previously expected 29 Apr 14:50:00

27 Apr 14:57:49
Details
27 Apr 14:56:58
Previously Openreach had advised that they intend to run a trial starting today on a small set of lines; where devices aren’t retransmission compatible in the upstream to see if changing certain parameters removes the latency and maintains the other benefits of retransmission. They have now advised us that the trial start date has been put back by two weeks (no idea why)

So if you have an FTTC line that is affected by this then please drop an email to support and we can include it in the list of affected lines that we will get included in the trial.

Update
11 May 11:07:12
Openreach have advised they will start loading the new DLM profiles to lines on Tuesday morning as part of regular DLM runs. Customers that are on the trial will notice a loss of sync when the new profiles are updated.
Started 27 Apr 14:51:39

25 Apr 18:46:00
Details
25 Apr 18:48:19
There was an unexpected blip in routing - we are looking in to it.
Started 25 Apr 18:44:00
Closed 25 Apr 18:46:00
Previously expected 25 Apr 22:46:00

20 Apr 09:54:30
Details
20 Apr 09:54:30
Customers will have received an email from us. Apologies for not PGP signing it. It asks you to go to a secure link on our control pages and confirm (one click) that you consent to receive notices via email.

Yes, I know it is crazy, and it is already part of our terms, and you already know we email notices, and that this email is a notice we have emailed you... Sorry but OFCOM insist we get *explicit* consent to send some notices we send.

We'd appreciate it if you just click the link and then the confirm button.

We'll email you again if you don't, sorry. If you are not happy about this, please do complain to OFCOM. Thank you.

Update
21 Apr 18:23:01
We have resent the email to all of those that have not followed the link and confirmed. This time, PGP signed. Sorry for any concern the previous email caused.
Update
21 Apr 18:29:59
I'd also like to thank the *thousands* of people that have confirmed their consent so far.
Started 19 Apr
Expected close 1 Jun

17 Apr 15:54:16
Details
15 Apr 13:16:15
Some customers on the Bradwell Abbey exchange are currently experiencing an outage. We have received reports from FTTP customers, however this may also affect customers using other services. BT have advised that they are currently awaiting a delivery for a new card at this exchange. We will chase BT for updates and provide them as we receive them.
Update
15 Apr 15:47:41
I have requested a further update from BT.
Update
16 Apr 08:07:15
Openreach AOC and PTO are investigating further at this time. We will reach out for an update later today.
Update
16 Apr 10:32:55
BT have advised that a Cable down is the root cause at this time.
Update
16 Apr 15:51:50
PTO are still onsite. I have asked for an ECD, however OpenReach are not supplying that information, due to being fibre work.
Update
17 Apr 10:19:33
OpenReach have stated, they are hoping for a completion on the fibre today and resource is being tasked out. OpenReach have stated this is only an estimate and not set in stone.
Update
17 Apr 14:49:46
Some customers are reporting a restored service. BT advise that teams are still on site to resolve this P1 issue.
Update
17 Apr 15:55:25
The cable down issue affecting customers using the Bradwell Abbey exchange has now been resolved.
Started 15 Apr 12:55:00 by AAISP Staff
Closed 17 Apr 15:54:16
Cause BT

16 Apr 16:00:24
Details
27 Mar 14:03:52
We are seeing packet loss on all lines connected through 21cn-BRAS-RED8-SL the loss is all through the day/night started 10:08 on the 25th. This has been reported to BT
Update
27 Mar 14:07:22
Here is an example graph:
Update
30 Mar 14:37:04
BT claimed to have fixed this but our monotoring is still seeing the loss, BT chased further
Broadband Users Affected 0.01%
Closed 16 Apr 16:00:24

16 Apr 15:59:33
Details
2 Feb 10:10:46
We are seeing low level packet loss on BT lines connected to the Wapping exchange - approx 6pm to 11pm every night. Reported to BT...
Update
2 Feb 10:13:57
Here is an example graph:
Update
3 Feb 15:55:40
Thsi has been escalated further with BT
Update
4 Feb 10:27:37
Escalated further with BT, update due after lunch
Update
11 Feb 14:18:00
Still not fixed, we are arming yet another rocket to fire at BT smiley
Update
24 Feb 12:58:51
escalated further with BT, update due by the end of the day.
Update
2 Mar 10:00:11
Again the last few users seeing packet loss will be moved onto another MSAN in the next few days.
Update
12 Mar 12:02:57
Updatew expected in the next few hours
Update
17 Mar 11:19:48
A further escalation has been raised on this, update by the end of the day
Update
30 Mar 15:35:32
This has been escalated to the next level
Broadband Users Affected 0.09%
Started 2 Feb 10:09:12 by AAISP automated checking
Closed 16 Apr 15:59:33

13 Apr 15:01:38
Details
13 Apr 14:51:55
There was an issue with two of our routers - a few lines dropped, and are reconnecting. Routing was affected for a minute or two. We're investigating.
Resolution Service has recovered as expected. We'll see if we can find the underlying cause. Sorry for any inconvenience.
Started 13 Apr 14:46:46
Closed 13 Apr 15:01:38
Previously expected 13 Apr 14:50:00

7 May 08:33:30
Details
2 Apr 15:48:08
We expect to do some router upgrades, including normal rolling LNS upgrades over the next week as a new release of the FireBrick is expected to be released shortly. This should have little or no disruption, as usual.
Update
9 Apr 12:52:05
This was a bit delayed and should start tonight, and be ongoing in to the weekend.
Update
25 Apr 09:08:02
Further updates this weekend (25/26)
Started 3 Apr
Closed 7 May 08:33:30
Previously expected 1 May

2 Apr 16:02:22
Details
17 Mar 12:38:27
We are seeing higher than normal evening time latency on the Wrexham exchange, it is not every night but it does suggest BT are running another congested link. This has been reported to them and we will update thia as and when they get back to us.
Update
17 Mar 12:41:51
Here is an example graph:
Update
20 Mar 14:36:18
It has looked better the last two eveings but it's still being investigated as the BT links were probably less busy.
Broadband Users Affected 0.01%
Started 15 Mar 12:36:07 by AAISP Staff
Closed 2 Apr 16:02:22

2 Apr 11:57:32
Details
1 Apr 10:00:06
Some customers connected through Gloucestershire are affected by an ongoing TalkTalk major service outage. Details below: Summary

Network monitoring initially identified total loss of service to all customers connected to 2 exchanges in the Gloucester area. Our NOC engineers re-routed impacted traffic whilst virgin media engineers carried out preliminary investigations. Virgin media restoration work subsequently resulted in several major circuits in the Gloucester area to fail.

This has resulted in a variety of issues for multiple customers connected to multiple exchanges. Our NOC engineers have completed re-routing procedures to restore service for some customers with other customers continuing to experience total loss of service due to capacity limitations. Impact: Tigworth, Witcombe and Painswick exchanges

Hardwicke and Barnwood exchanges – experiencing congestion related issues.

Cheltenham and Churchdown – experiencing congestion related issues.

experiencing congestion related issues Stroud, Stonehouse, Whitecroft, Blakeney, Lydney, Bishops Cleeve, Winchcombe, Tewkesbury, Bredon exchanges.

Update
1 Apr 10:31:30
TT have advised that splicing of the affected fibre is still ongoing. There is no further progressive updates at this time. Further updates will be sent out shortly.
Update
2 Apr 11:57:26
Root cause analysis identified a major Virgin Media fibre break due to third party contractor damage as being the cause of this incident. Service was fully restored when Virgin Media Fibre engineers spliced new fibre. Following this we received confirmation that service had returned as BAU. TalkTalk customers would have been automatically rerouted and would have experienced only a momentary Loss of Service. An observation period has been carried out verifying network stability and as no further issues have been reported this incident will be closed with further investigations into the cause being tracked via the Problem Management process
Closed 2 Apr 11:57:32

27 Mar 09:00:00
Details
25 Mar 21:48:13
Since the 24th March we have been seeing congestion on TalkTalk lines on the Shepherds Bush exchange. This has been reported to TalkTalk. Example graph:
Update
26 Mar 10:51:48
TalkTalk say they have fixed this. We'll be checking overnight to be sure smiley
Update
26 Mar 22:27:33
Lines are looking good.
Resolution

We had this feedback from TalkTalk regarding this congestion issue:

Shepherds Bush has three GigE backhauls to two different BNG's - there was some a software process failure and restart on one of these devices on Tuesday morning which had two of the three backhauls homed to it. As a result all customers redialled to the one 'working' BNG in the exchange - normally when this happens we will calculate whether or not the backhaul can handle that number of customers and if not manually intervene, in this case however a secondary knock on issue meant that our DHCP based customers (FTTC subs) were sent through the same backhaul and the calculation was inaccurate.

If the PPP session was restarted they would have reconnected on their normal BNG and everything should be OK - we've just made this change manually moving subscribers over - still have a couple of lines on the backup BNG so will monitor if there are any issues and take any necessary actions to resolve.

Started 24 Mar 17:00:00
Closed 27 Mar 09:00:00

17 Mar 11:18:55
Details
20 Jan 12:53:37
We are seeing low level packet loss on some BT circuits connected to the EUSTON exchange, this has been raised with BT and as soon as we have an update we will post an update here.
Update
20 Jan 12:57:32
Here is an example graph:
Update
22 Jan 09:02:48
We are due an update on this one later this PM
Update
23 Jan 09:36:21
BT are chasing this and we are due an update at around 1:30PM.
Update
26 Jan 09:41:39
Work was done over night on the BT side to move load onto other parts of the network, we will check this again this evening and report back.
Update
27 Jan 10:33:05
We are still seeing lines with evening packet loss but BT don't appear to understand this and after spending the morning arguing with them they have agreed to investigate further. Update to follow.
Update
28 Jan 09:35:28
Update from BT due this PM
Update
29 Jan 10:33:57
Bt are again working on this but no further updates will be given until tomorrow morning
Update
3 Feb 16:19:06
This one has also been escalated further with BT
Update
4 Feb 10:18:11
BT have identified a fault within their network and we have been advised that an update will be given after lunch today
Update
11 Feb 14:16:56
Yet another rocket on it's way to BT
Update
24 Feb 12:59:20
escalated further with BT, update due by the end of the day.
Update
2 Mar 09:59:19
STill waiting for BT to raise an emergency PEW, the PEW (planned engineering work) will sort the last few lines where we are seeing peak time packet loss)
Update
12 Mar 12:03:57
I need to check this tonight as bT think it is fixed, I will post an update back tomorrow
Broadband Users Affected 0.07%
Started 10 Jan 12:51:26 by AAISP automated checking
Closed 17 Mar 11:18:55
Previously expected 21 Jan 16:51:26

13 Mar 22:57:53
Details
13 Mar 22:44:00
TalkTalk lines lost connection at about 10:30, and are reconnecting at the moment.
Update
13 Mar 22:47:49
About 80% of lines have now reconnected.
Update
13 Mar 22:58:06
Most lines are back.
Resolution Confirmed as a fault within the TalkTalk network that affected us and other ISPs.
Started 13 Mar 22:30:00
Closed 13 Mar 22:57:53

6 Mar 13:00:00
Details
5 Mar 10:54:01
We are seeing quite a few lines on the Durham and NEW BRANCEPETH exchange with a connection problem. Customers may have no internet access and their router constantly logging in and out.

We have reported this fault to BT and they are investigating. It looks like the BRAS has a fault.

Update
5 Mar 16:25:28
We have been chasing this with BT throughout the day; their tech team are still investigating.
Update
6 Mar 09:16:19
We still have a few lines off and we are on the phone to BT now chasing this. Update to follow.
Update
6 Mar 13:48:38
BT appear to have a broken LAG (link aggregation group) and as a work around we have had to change one of our end point IP addresses and the affected customers are back on line. This is just a work around and hopefully BT will shortly fix their end.
Started 5 Mar 02:00:00
Closed 6 Mar 13:00:00

5 Mar 18:15:01
Details
4 Mar 17:44:38
Work this evening went pretty much as planned - we added extra diagnostics to try and identify something unexpected in routing. We are going to do some more investigation tomorrow. We expect there to be little or no impact on services once again.
Resolution Work completed, again with minimal disruption.
Started 5 Mar 17:00:00
Closed 5 Mar 18:15:01
Previously expected 5 Mar 18:00:00

4 Mar 17:41:52
Details
4 Mar 12:48:36
We plan to upgrade a couple more routers this evening. It should have no impact for most of these, but one of them is likely to cause a slight blip on TalkTalk lines.
Resolution The work has been completed and without the TalkTalk blip. Some routing was a bit odd to/from Maidenhead, and we are looking in to that, but the changes seem to have worked so far. We expect we'll do something similar tomorrow.
Started 4 Mar 17:00:00
Closed 4 Mar 17:41:52
Previously expected 4 Mar 18:00:00

4 Mar 10:03:07
Details
2 Mar 06:17:18
Many of our customer broadband lines suffered a blip just after 2am. We're still investigating that, but it seems our RADIUS accounting got behind due to the high number of lines flapping. It looks like accounting has caught up now, but it will mean that we sent out some delayed notifications over night. This could result in, for example, line down/up notification emails delayed by several hours. The time stamp in the notification should show if this is the case.
Closed 4 Mar 10:03:07

3 Mar 19:46:10
Details
3 Mar 19:29:41
We are planning a minor upgrade on a router this evening which should have no impact on normal working.
Resolution Updates done
Started 3 Mar 19:29:03
Closed 3 Mar 19:46:10
Previously expected 3 Mar 23:29:03

24 Feb 13:00:22
Details
2 Feb 11:21:40

Below is a list of exchanges that BT plan to WBC enable between April - June this year.

This is for information only and we will attempt to bulk migrate customers to the 21CN network as and when they are enabled.

ABERCHIRDER
ANCRUM
ANGLE
ANSTEY MILLS
ASHBURY
AVEBURY
BARLASTON
BEAL
BERRIEW
BILLESDON
BIXTER
BOBBINGTON
BODFARI
BRENT KNOLL
BRETTON
BROMESBERROW
BUCKLAND NEWTON
BULWICK
BURGH ON BAIN
BURRELTON
CAPUTH
CHOLESBURY
CHURCHSTANTON
CLANFIELD
COBERLEY
COLINSBURGH
CRANFORD
CREATON
CRONDALL
CRUCORNEY
CYNWYL ELFED
DALE
DINAS CROSS
DINAS MAWDDWY
DITTON PRIORS
DOLWEN
DUNECHT
DUNRAGIT
DURLEY
EARLDOMS
EAST HADDON
EAST MEON
EDDLESTON
FAYGATE
GAMLINGAY
GAYTON
GLAMIS
GLENLUCE
GREAT CHATWELL
GREENLAW
HAMNAVOE
HUXLEY
ILMINGTON
INNERWICK
KELSHALL
KINLET
KIRKCOLM
LANGHOLM
LANGTREE
LITTLE STEEPING
LLANDDAROG
LLANFAIRTALHAIARN
LLANFYLLIN
LLANNEFYDD
LYDFORD
LYONSHALL
MANORBIER
MICHELDEVER
MIDDLETON SCRIVEN
MIDDLETON STONEY
MILLAND
MILTON ABBOT
MUNSLOW
MUTHILL
NANTGLYN
NEWNHAM BRIDGE
NORTH CADBURY
NORTH CRAWLEY
NORTH MOLTON
NORTHWATERBRIDGE
OFFLEY
PARWICH
PENTREFOELAS
PUNCHESTON
SHEERING
SHEPHALL
STEBBING
STOKE GOLDINGTON
STOW
SUTTON VENY
TALYBONT ON USK
TEALBY
TWINSTEAD
UFFINGTON
WATERHOUSES
WITHERIDGE
WIVELSFIELD GREEN
WOBURN
LEWDOWN
ROMSLEY


24 Feb 12:57:31
Details
11 Feb 10:17:36
We are seeing evening congestion on the Wrexham exchange, also off that two other BRAS's are affected. They are: 21CN-BRAS-RED6-SF 21CN-BRAS-RED7-SF Customers can check which BRAS/exchange they are connected to from our control pages
Update
11 Feb 10:27:08
Here is an example graph:
Update
13 Feb 11:39:14
We are chasing BT for an update and as soon as we have further news we wil update this post.
Update
16 Feb 10:20:43
It looks like the peak time latency just went away Thursday evening with no report from BT that they actually changed something. We will continue monitoring for the next few days to ensure it really has gone away.
Broadband Users Affected 0.05%
Started 11 Feb 10:12:08 by AA Staff
Closed 24 Feb 12:57:31

13 Feb 15:31:16
Details
13 Feb 14:29:06
We currently supply the Technicolor TG582 for most ADSL services, but we are considering switching to a new router, the ZyXEL VMG1312-B

It is very comprehensive and does both ADSL and VDSL as well as bridging and wifi. It means we can have one router for all service types. As some of you may know, BT will be changing FTTC to be "wires only" next year, and so a VDSL router will be needed.

We have a small number available now for people to trial - we want to test the routers, our "standard config" and the provisioning process.

Please contact trial@aa.net.uk or #trial on the irc server for more information.

P.S. Obviously it does Internet Protocol, the current one, IPv6 and the old one IPv4

Obviously this initial trial is limited number of routers which we are sending out at no charge to try different scenarios. However, we expect to be shipping these as standard later in the month, and they will be available to purchase on the web site.

Update
13 Feb 15:49:08
Thanks for all the emails and IRC messages about trialling the new routers. We will contact customers back on Monday to arrange shipping of the units.
Update
16 Feb 10:43:54
We now have enough trialists for the new router, we will contact a selection of customers today to arrange delivery of the routers. Thanks
Started 13 Feb 14:25:34

15 Feb 12:24:53
Details
12 Feb 18:00:36
The Technicolor routers we supply have a factory default config which connects to us and operates a default setup. This is applied if someone uses the RESET button on the routers.

We have identified that a few dozen of these routers are in this state, which is not correct.

As part of work we are doing for some new routers we plan to start shipping soon, we have made it that any router logging in using the factory default will automatically be updated to have the correct config.

This will likely cause the graph to reset and the LNS in use depends on the login, but it will also set the WiFi SSID correctly, and other parameters. So users may see a change.

If you have any issues, do contact support.

Resolution The change in process has meant a number of routers have been auto-provisioned as expected, the remainder will when they next connect. Any issues, do contact support.
Started 12 Feb 17:00:00
Closed 15 Feb 12:24:53
Previously expected 14 Feb

5 Feb 13:07:52
Details
8 Jan 15:44:04
We are seeing some levels of congestion in the evening on the following exchanges: BT COWBRIDGE, BT MORRISTON, BT WEST (Bristol area), BT CARDIFF EMPIRE, BT THORNBURY, BT EASTON, BT WINTERBOURNE, BT FISHPONDS, BT LLANTWIT MAJOR. These have been reported to BT and they are currently investigating.
Update
8 Jan 15:56:59
He is an example graph:
Update
9 Jan 15:21:53
BT have been chased further on this as they have not provided an update as promised.
Update
9 Jan 16:19:48
We did not see any congestion over night on the affected circuits but we will continue monitoring all affected lines and post another update on Monday.
Update
12 Jan 10:37:32
We are still seeing congestion on the Exchanges listed above between the hours of 20:00hrs and 22:30hrs. We have updated BT and are awaiting their reply.
Update
20 Jan 12:52:05
We are now seeing congestion starting from 19:30 to 22:30 on these exchanges. We are awaiting an update from BT.
Update
21 Jan 11:13:44
BT have sent this into the TSO team, we are to await their investigation results. We will provide another update as soon as we have a reply.
Update
22 Jan 09:06:14
An update is expected on this tomorrow
Update
23 Jan 09:33:48
This one is still being investigated at the moment, and may need a card or fiber cable fitting, Will chase this for an update later on in the day.
Broadband Users Affected 0.30%
Started 8 Jan 15:40:15 by AA Staff
Closed 5 Feb 13:07:52

29 Jan 10:07:29
Details
27 Jan 11:48:41
We are currently seeing congestion in the evening between the hours of 8PM and 11PM on the following BRASs: BRAS 21CN-BRAS-RED4-CF-C, BRAS 21CN-ACC-ALN12-CF-C, BRAS 21CN-BRAS-RED8-CF-C. We have raised this into BT and their Estimated completion date is: 29-01-2015 11:23 We will update you as soon as we have some more information.
Update
27 Jan 12:02:35
Here is an example graph:
Resolution Nothing back from BT but we suspect they have increased capacity accorss the links, any further news on this we will update the post.
Started 27 Jan 11:44:56
Closed 29 Jan 10:07:29

24 Jan 08:17:21
Details
23 Jan 08:35:26
In addition to all of the BT issues we have ongoing (and affecting all ISPs), we have seen some signs of congestion in the evening last night - this is due to planned switch upgrade work this morning. Normally we aim not to be the bottleneck, as you know, but we have moved customers on to half of our infrastructure to facilitate the switch change, and this puts us right on the limit for capacity at peak times. Over the next few nights we will be redistributing customers back on to the normal arrangement of three LNSs with one hot spare, and this will address the issue. Hopefully we have enough capacity freed up to avoid the issue tonight. Sorry for any inconvenience. Longer term we have more LNSs planned as we expand anyway.
Update
24 Jan 07:30:14
The congestion was worse last night, and the first stage of moving customers back to correct LNSs was done over night. We are completing this now (Saturday morning) to ensure no problems this evening.
Resolution Lines all moved to correct LNS so there should be no issues tonight.
Started 22 Jan
Closed 24 Jan 08:17:21
Previously expected 24 Jan 08:30:00

28 Jan 09:38:34
Details
4 Jan 09:45:22
We are seeing evening congestion on the Bristol North exchange, incident has been raised with BT and they are investigating.
Update
19 Jan 09:51:48
Here is an example graph:
Update
22 Jan 08:58:26
The fault has been escalated further and we are expected an update on this tomorrow.
Update
23 Jan 09:37:14
No Irams/Pew has been issued yet, and no further updates this morning. We are chasing BT. Update is expected around 1:30PM today.
Update
26 Jan 09:36:18
BT are due to update us on this after 3Pm today
Update
26 Jan 13:24:05
BT are looking to change the SFP port on the BRAS, we are chasing time scales on this now.
Update
26 Jan 14:16:43
This work will take place between 02:00 and 06:00 tomorrow morning
Update
27 Jan 09:23:21
Chasing BT to confirm the work was done over night, update to follow
Update
27 Jan 11:25:18
Nope, the work was postponed to this evening so we won't know whether they have fixed it until Wednesday evening. We will see.....
Update
28 Jan 09:38:34
Wow. Another BT congested link has been fixed over night.
Resolution BT changed the SFP port on the BRAS
Broadband Users Affected 0.01%
Started 4 Jan 09:45:22
Closed 28 Jan 09:38:34
Previously expected 29 Jan 13:23:24

28 Jan 09:25:23
Details
21 Jan 09:44:42
Our minitoring has picked up further congestion within the BT network causing high latency between 6pm-11pm every night on the following BRAS's. This is affecting BT lines only and in the Bristol and South/South west Wales areas. 21CN-BRAS-RED3-CF-C 21CN-BRAS-RED6-CF-C An incident has been raised with BT and we will update this post as and when we have updates.
Update
21 Jan 09:47:51
Here is an example graph:
Update
22 Jan 08:46:12
We are expecting a resolution on the tomorrow - 2015-01-23
Update
23 Jan 09:35:26
This one is still with the Adhara NOC team. They are trying to solve the congestion problems. Target resolution is today 23/1/15, we have no specific time frame so we will update you as soon as we have more information from BT.
Update
26 Jan 10:03:08
we are expecting an update on this later this afternoon
Update
26 Jan 16:23:32
BT are seeing some errors on slot 7 on one of the 7750’s, they looking to swap it over this evening, then they will monitor it, will update you once I get any further update.
Update
27 Jan 09:20:48
We are checking with BT whether or not a change was made over night.
Update
28 Jan 09:25:17
BT have actually cleared the congestion. We will monitor this very closely though.
Broadband Users Affected 0.03%
Started 4 Jan 18:00:00 by AA Staff
Closed 28 Jan 09:25:23
Previously expected 28 Jan 09:20:53

27 Jan 15:45:12
Details
27 Jan 13:45:04
There appears to be a problem with one of BT's BRAS's (21CN-BRAS-RED3-BM-TH) where customers are unable to connect. We are speaking to BT about this now and will update this post ASAP.
Update
27 Jan 13:52:57
BT 'tech services' are aware and dealing as we speak ....
Update
27 Jan 13:54:12
There are engineers on site already!
Update
27 Jan 15:45:36
WOW. BT have fixed their BRAS fault in record time. smiley
Broadband Users Affected 0.01%
Started 27 Jan 12:19:21
Closed 27 Jan 15:45:12
Previously expected 27 Jan 17:42:21

23 Jan 06:47:57
Details
19 Jan 09:55:58
We are replacing one of our core switches in London on Friday from 6AM. This should not be service affecting, but should be considered an 'at risk' period. We'll update this post as this work is carried out.
Update
21 Jan 15:01:16
This has been rescheduled for Friday 6AM.
Update
23 Jan 06:23:05
Work on this is about to start.
Update
23 Jan 06:48:22
This work has been completed.
Started 23 Jan 06:00:00
Closed 23 Jan 06:47:57

22 Jan 09:48:14
Details
13 Jan 12:17:05
We are seeing low level packet loss on the Hunslet exchange (BT tails) this has been reported to BT. All of our BT tails connected to the Hunslet exchange are affected.
Update
13 Jan 12:27:11
Here is an example graph:
Update
15 Jan 11:50:15
Having chased BT up they have promised us an update by the end of play today.
Update
16 Jan 09:07:51
Bt have identified a card fault within their network. We are just waiting for conformation as to when it will be fixed.
Update
19 Jan 09:31:11
It appears this is now resolved - well BT have added extra capacity on the link: "To alleviate congestion on acc-aln2.ls-bas -10/1/1 the OSPF cost on the backhauls in area 8.7.92.17 to acc-aln1.bok and acc-aln1.hma have been temporarily adjusted to 4000 from 3000. This has brought traffic down by about 10 to 15 % - and should hopefully avoid the over utilisation during peak"
Resolution Work has been completed on the BT network to alleviate traffic
Broadband Users Affected 0.01%
Started 11 Jan 12:14:28 by AAISP Pro Active Monitoring Systems
Closed 22 Jan 09:48:14

19 Jan 12:01:39
Details
14 Jan 11:23:00
We have reported congestion effecting TT BERMONDSEY in the evenings starting from the 8th of Jan. Updates will follow when we have them. Thanks for your patience.
Update
14 Jan 11:28:46
Here is an example graph
Update
15 Jan 10:31:10
Talk Talk have now fixed the congestion issue and we are no longer seeing packet loss.
Started 8 Jan 11:20:05

19 Jan 11:28:57
Details
19 Dec 2014 09:44:48
Today the CVE-2014-9222 router vulnerability AKA 'misfortune cookie' has been announced at http://mis.fortunecook.ie/ This is reported to affect many broadband routers all over the world. The web page has further details.
We are contacting our suppliers for their take on this, we'll post follow-ups to this status post shortly.
It is also worth noting that at the time of writing CVE-2014-9222 is still 'reserved': http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-9222
Update
19 Dec 2014 09:52:28
Technicolor Routers:- These routers are not (yet?) on the list, we are awaiting a response from Technicolor regarding this.
Update: Technicolor say "We don’t use that webserver, so not impacted”"
Update
19 Dec 2014 09:59:46
ZyXEL P-660R-D1: This router is on the list. We are awaiting a response from ZyXEL though. We do already have this page regarding the web interface on ZyXELs: http://wiki.aa.org.uk/Router_-_ZyXEL_P660R-D1#Closing_WAN_HTTP and closing the Web server from the WAN may help with this vulnerability.
Update: The version of RomPager (the web server) on ZyXELs that we have been shipping for some time is 4.51. Allegedly versions before 4.34 are vulnerable, so they may not be vulnerable. You can tell the version with either:
wget -S IP.of.ZyXEL
or
curl --head IP.of.ZyXEL
Update 2015-01-07: P-660R-D1 Not affected: http://www.zyxel.com/support/ZyXEL_Helps_You_Guard_against_misfortune_cookie_vulnerability.shtml
Update
19 Dec 2014 10:00:57
Dlink 320B: We supply these in Bridge mode and therefore are not vulnerable.
Update
19 Dec 2014 10:02:38
FireBrick: Firebricks are not vulnerable.
Started 19 Dec 2014 09:00:00

16 Jan 09:16:49
Details
15 Jan 14:26:38
Just before 2PM today a number of TalkTalk circuits dropped out, it looks like they have all now come back on line. We are investigation this with TalkTalk
Update
15 Jan 14:54:39
TT are investigating further but initial response from them "nothing is presenting me with an obvious answer other than what appears to have been a connectivity problem to HEX" Update to follow
Update
16 Jan 09:17:35
Update from TT. Summary Network monitoring has identified that Wholesale Business customers across the country may have experienced a brief loss of service between 14:00 and 14:05. Network Monitoring completed by our NOC has identified that there was a drop of traffic at these times between a Network Core Router at the Brentford Data Centre (NCR002.BRE) and a Redback router (LTS001.HEX). This subsequently caused Wholesale Business customers who route through Harbour exchange to experience a loss of service.
Resolution Technical / Suspected Root Cause Investigations by our Network Support have identified that this issue occurred due to planned LTS work under SR8753. This work caused the queues on the LTS to fill up and caused a CPU spike, which in turn caused the tunnels to drop. There are plans to increase circuit capacity going forward to ease bandwidth levels and prevent a repeat of this issue.
Broadband Users Affected 1%
Started 15 Jan 14:24:54
Closed 16 Jan 09:16:49
Cause Carrier
Previously expected 15 Jan 18:24:54

13 Jan 11:46:40
Details
18 Dec 2014 20:00:52
The working days between Christmas and New Year are "Christmas" rate, this means that any usage on 29th, 30th, and 31st December is not counted towards your Units allowance. As usual, bank holidays are treated as 'Weekend' rate.
(This doesn't apply to Home::1 or Office::1 customers.)
We wish all out customers a Merry Christmas!
Started 18 Dec 2014 19:00:00

11 Jan 11:36:06
Details
11 Jan 11:14:41
We may have to restart one or two of our LNSs in the early hours of Monday morning as there seems to be an issue with them. This is not affecting service at present but does mean we do not have any of the normal graphs which are essential to diagnostics and fault handling. Lines should reconnect promptly and ideally only be off for a few seconds, but, as usual, this very much depends on the routers and some lines make take a few minute to reconnect. There may be a second controlled PPP restart for some lines that end up on the wrong LNS once lines have stabilised.
Resolution False alarm, work cancelled.
Broadband Users Affected 66%
Started 12 Jan
Closed 11 Jan 11:36:06
Previously expected 12 Jan 07:00:00

10 Jan 20:00:00
Details
10 Jan 19:44:03
Since 19:20 we have seen issues on all TalkTalk backhaul lines. Investigating
Update
10 Jan 20:08:08
Looks to be recovering
Update
10 Jan 21:32:01
Most lines are up as of 8pm. We'll investigate the cause of this.
Started 10 Jan 19:20:00
Closed 10 Jan 20:00:00

10 Jan 15:35:00
Details
10 Jan 10:13:09
We are investigating a problem affecting some wholesale customers. This seems to be a data centre connectivity fault. Updatea to follow.
Update
10 Jan 10:23:40
This is related to a fault with Datahop,outside of our network. They are aware and investigating.
Update
10 Jan 15:37:12
Our Datahop ports are now back online. (Ironically, they came on line whilst waiting on hold for their NOC!). Wholesales lines are starting to reconnect. We suspect a faulty switch is to blame within Datahop.
Update
10 Jan 21:09:52
Datahop confirm this was caused by a faulty switch.
Started 10 Jan 09:20:00
Closed 10 Jan 15:35:00

12 Dec 2014 11:00:40
Details
11 Dec 2014 10:42:15
We are seeing some TT connected lines with packetloss starting at 9AM yesterday and today. The loss lasts until 10AM and then there continues a low amount of loss. We have reported this to TalkTalk
Update
11 Dec 2014 10:46:34
This is the pattern of loss we are seeing:
Update
12 Dec 2014 12:00:04
No loss has been seen on these lines today. We're still chasing TT for any update though.
Resolution The problem went away... TT were unable to find the cause.
Broadband Users Affected 7%
Started 11 Dec 2014 09:00:00
Closed 12 Dec 2014 11:00:40

11 Dec 2014 14:15:00
Details
11 Dec 2014 14:13:58
BT issue affecting SOHO AKA GERRARD STREET 21CN-ACC-ALN1-L-GER. we have reported to this BT and they are now investigating.
Update
11 Dec 2014 14:19:33
BT are investigating, however the circuits are mostly back online.
Started 11 Dec 2014 13:42:11 by AAISP Pro Active Monitoring Systems
Closed 11 Dec 2014 14:15:00
Previously expected 11 Dec 2014 18:13:11 (Last Estimated Resolution Time from AAISP)

02 Dec 2014 09:05:00
Details
01 Dec 2014 21:54:24
All FTTP circuits on Bradwell Abbey have packetloss. This started at about 23:45 on 30th November. This is affecting other ISPs too. BT did have an Incident open, but this has been closed. They restarted a line card last night, but it seems the problem has been since the card was restarted. We are chasing BT.
Example graph:
Update
01 Dec 2014 22:38:39
It has been a struggle to get the front line support and the Incident Desk at BT to accept that this is a problem. We have passed this on to our Account Manager and other contacts within BT in the hope of a speedy fix.
Update
02 Dec 2014 07:28:40
BT have tried doing something overnight, but the packetloss still exists at 7am 2nd December. Our monitoring shows:
  • packet loss it stops at 00:30
  • The lines go off between 04:20 and 06:00
  • The packet loss starts again at 6:00 when they come back onine.
We've passed this on to BT.
Update
02 Dec 2014 09:04:56
Since 7AM today, the lines have been OK... we will continue to monitor.
Started 30 Nov 2014 23:45:00
Closed 02 Dec 2014 09:05:00