Order posts by limited to posts

31 Aug 01:00:00
Details
Posted: 31 Aug 08:36:41
TalkTalk have lots of small planned work projects happening at the moment. These generally happen from midnight and affect a small number of exchanges at a time. The work does cause service to stop for 30 minutes or longer. TalkTalk publish this information on their status page: https://managed.mytalktalkbusiness.co.uk/network-status/
We are looking at ways of adding these planned works to the Control Pages so as to make it clearer for customers if they are going to be afected.
Started 31 Aug 01:00:00
Previously expected 31 Oct 07:00:00

9 Mar 20:00:00
Details
Posted: 8 Mar 12:29:14

We continue to work with TalkTalk to get to the bottom of the slow throughput issue as described on https://aastatus.net/2358

We will be performing some routing changes and tests this afternoon and this evening, we are not expecting this to cause any drops for customers, but this evening there will be times when throughput for 'single thread' downloads will be slow. Sorry for the short notice, please bear with us, this is being a tricky fault to track down.

Update
8 Mar 22:39:39
Sorry, due to TalkTalk needing extra time to prepare for their changes this work has been moved to Thursday 9th evening.
Started 9 Mar 20:00:00
Update was expected 9 Mar 23:00:00

Yesterday 21:18:37
Details
Posted: 16 Oct 14:03:30

There are lots of news articles and discussions about the 'KRACK' attack vulnerability affecting WiFi client devices.

In summary, this affects WPA2 (and WPA3) (as well as being an additional insecurity with TKIP) And is actually a bug in the WiFi spec - ie the design wasn't thought out properly. So any implementation which follows the spec is vulnerable. There is more technical information about this in the links below.

From an customer of AAISP point of view, we do sell DSL routers with WiFI as well as WiFi access points but, this is a vulnerability in WiFi clients rather than the routers themselves.

Generally, the fix for this vulnerability is on the client side - ie the computer or mobile device connecting to a WiFi network, and so customers should look for software updates for their devices and operating systems. There are links below regarding devices we are involved with which contain further information.

We'll add further information to this post as we receive it.

Update
16 Oct 14:04:01

For more information see: https://www.krackattacks.com/ and all the gory details are in the paper: https://papers.mathyvanhoef.com/ccs2017.pdf

WiFi device specific information:

Remember the main devices to patch are your devices such as computers, phones, tablets etc - once updates have been released and many devices will already have been patched if they are up to date. Updates to Routers and access points will will address the problem when they are acting as a WiFi client themselves and so won't really help if your devices are still unfixed.

Started 16 Oct 10:00:00

21 Nov 18:00:00
Details
Posted: 21 Nov 13:32:59
We are upgrading some routers today - this generally has no impact, but there is a risk of some small issues. Sorry for very short notice.
Started 21 Nov 13:00:00
Closed 21 Nov 18:00:00
Previously expected 21 Nov 19:00:00

17 Nov 18:34:27
Details
Posted: 17 Nov 11:36:33

We are seeing a denial of service attack, which is causing more problems that usual, and this is disrupting traffic to some customers - but it is moving, and so different customers at different times.

Obviously we are working on this, and unfortunately cannot say a lot more of the details.

Update
17 Nov 12:09:40
We are still seeing problems, customer on this LNS would have seen drops and routing problems. We are working on this.
Update
17 Nov 12:10:32
This problem has also been affecting some of our transit routes, and so routing to parts of the internet will have had problems too.
Update
17 Nov 12:42:15
We are working through this still, we have moved lines off A.Gormless, and have had further problems with those lines. Please do bear with us, we hope things to calm down shortly.
Update
17 Nov 13:39:21
We cannot go in to a lot of detail but I will say this is a complete new sort of attack. We have made some changes and will be reviewing ways we can mitigate attacks like this in the future. I'll re-open this issue if problems continue. Thank you all for your patience.
Update
17 Nov 13:54:44
Hmm, that attacker is clearly back from lunch.
Update
17 Nov 15:15:18
Not gone away - we are working on more...
Update
17 Nov 16:21:02
This now appears to be affecting VoIP too.
Update
17 Nov 17:19:54
We're rebalancing some lines due to the issues early morning today as per https://aastatus.net/2457 and additionally due to today's issues.
Some PPP sessions will disconnect and shortly reconnect. This is to fix an imbalance in the number of sessions we have per LNS.
Update
17 Nov 17:34:50
The line rebalancing is fine, and mostly broadband is fine, but we are tackling a moving target aiming at various services on an ongoing basis.
Resolution Quiet for now, we are monitoring still.
Started 17 Nov 11:25:00
Closed 17 Nov 18:34:27

19 Nov 18:11:03
Details
Posted: 19 Nov 18:11:03
At the end of last week we installed three additional LNSs, all FireBrick FB6202 routers - these are the devices that sit between our carriers such as BT and TalkTalk and our network and that our broadband connections are terminated on. The addition of these three increase our capacity and helps spread broadband connection over more routers. We now have eleven live and one spare. These are the 'A-L.Gormless' named hosts that you'd see on the control pages etc.
Started 19 Nov 18:00:00

17 Nov 13:40:06
Details
Posted: 17 Nov 01:26:59
At 00:42, a large number of lines across all carriers disconnected, and then reconnected. Some lines may have taken longer than others to come back, however session numbers now are noted to have slowly recovered to their usual levels. During this outage, a significant number of BT lines have ended up biased to one LNS in particular which will need dealing with.
As session numbers have stabilised and traffic levels look normal, a further investigation into this event will follow in the morning, along with plans to move customers off of I.gormless where the large number of BT sessions have accumulated.
Update
17 Nov 10:50:48
We expect to do some PPP restarted early evening before the evening peak traffic to put lines back on the right LNS. This will not be all customers. We are then looking to do some PPP restarts over night during the weekend to distribute over the newly installed LNSs.
Resolution The original issue has gone away, because of other problems today (DoS attack) we expect to be rebalancing lines later in the day and over night anyway. Thank you for your understanding.
Broadband Users Affected 90%
Started 17 Nov 00:41:25 by AA Staff
Closed 17 Nov 13:40:06

10 Nov 12:48:12
Details
Posted: 10 Nov 12:17:54

OFCOM have today published their decision on automatic compensation for broadband and phone line faults. The result is a scheme adopted only by the major ISPs to pay compensation for delayed installs, delayed fault repair and missed appointments.

As a small ISP, we are relieved at this approach as the original proposals contained a number are areas of serious concern. This is good news for consumers generally and should hopefully mean that Openeach and back-haul carriers that we use put in place systems to pay automatic compensation (though OFCOM have not insisted on this). If this happens we will be able to pass on any compensation we receive automatically to AAISP customers as well.

So, whilst not part of the scheme, AAISP customers should benefit from automatic compensation in most cases.

We also hope, as do OFCOM, that in the 15 months lead up to the scheme starting, the likes of Openreach will actually improve services so as to avoid having to pay compensation. Obviously this will benefit all ISPs and their customers, not just those in the scheme.

Started 10 Nov 12:18:04

10 Nov 11:23:51
Details
Posted: 21 Oct 17:30:55
We have identified a small number of TalkTalk connected circuits that have 1-4% packetloss in the evenings between 7pm and 9pm. We have worked with TalkTalk NOC and have helped them to identify a link running at full capacity within their network. Work is still ongoing to fix this.
Update
21 Oct 17:42:22
To aid with TalkTalks investigations we have shutdown our interconnect in Harbour Exchange to TalkTalk. We still have plenty of capacity in Telehouse so this work is not service affecting.
Update
21 Oct 17:50:43
TalkTalk say: "NOC troubleshooting has identified that one of three 10 gig circuit between the LTS and the LDN at hex is reaching capacity between 19:30 and 21:30hrs and is the root cause of the packet loss."
Update
10 Nov 11:23:51
See: https://aastatus.net/2454 for details regarding testing the new TalkTalk network which will resolve this.
Update
Wednesday 21:33:35
packetloss on TalkTalk connected circuits has increased over the past day or so. We're happy to move customers to trial TalkTalk's new network, do get in touch with trial@aa.net.uk
Broadband Users Affected 1.50%
Started 18 Oct 19:00:00

9 Nov 15:47:52
Details
Posted: 9 Nov 15:47:52
"TalkTalk have built a new Juniper LTS solution in order to:
  • Increase the total subscribers per TalkTalk LTS
  • Increase of the throughput capacity per chassis
  • Assist with load balancing
  • Increase network resilience"

In other words, they have been working on a new network for some time which should see the end of the various minor congestion issues that we've been seeing and will mean the have ample capacity for the future.

Before we migrate all our customers over we are asking for some customers to test this new network. Testing simply means us making some changes and the customer changing their PPP username slightly. Everything else works the same.

If you would like to test, please send an email with your login to: trial@aa.net.uk and we'll get back to you with further instructions.

We are one of the first ISPs that will be using the new network and we expect to move all our customers over before the end of November but we have not set a date yet.

Update
Wednesday 16:04:33
Customers on the TalkTalk trial will be moved to a new LTS this afternoon. The LTS is the router at TalkTalks end of our links to them. This involves a PPP re-connect and this will be carried out by TalkTalk. Your router shoudl log back in within a few seconds. This new LTS has newer software which we're testing to see if some of the bugs we've reported are fixed. We'll post more about this shortly.
Started 9 Nov 15:30:00

7 Nov 15:30:00
Details
Posted: 1 Nov 17:22:57
We are upgrading one of our LINX peering ports to 10G in the afternoon of 2nd November. We do not expect this to affect customers in anyway.
Update
2 Nov 14:14:50
This work is being carried out now.
Update
6 Nov 12:10:27
We had to postpone this upgrade. It will now happen on Tuesday 7th November.
Update
7 Nov 13:47:00
This work is being carried out now.
Resolution This has been completed successfully.
Started 7 Nov 13:30:00
Closed 7 Nov 15:30:00

3 Nov 20:55:02
Details
Posted: 3 Nov 19:56:18
We had an unexpected reset of the 'B.Gormless' LNS at 19:45. This caused customers on this LNS to be disconnected. Most have reconnected now though.
Resolution This LNS has reset a few times in the past few months. We'll look at replacing the hardware.
Started 3 Nov 19:45:00
Closed 3 Nov 20:55:02

3 Nov 12:00:00
Details
Posted: 2 Nov 14:14:19

So as to facilitate some testing we're doing with TalkTalk, we are going to upgrade the software on the H.Gormless LNS. This will involve moving customers off this LNS first.

Therefore, customers on the H.Gormless LNS will have their PPP reset during the early hours of Friday 3rd November from 1AM. This will force your router to be logged off. It will then log back in to a new LNS. This usually happens very quickly.

The exact time will depend on your Line's 'LNS reset' setting, the default is 1AM, but you are able to pick the time. For more information about this process see: https://support.aa.net.uk/LNS_Switches

Update
3 Nov 15:15:47
There is a further switch back from I to H gormless tonight (Saturday morning). This means we can now do the testing we need with Talk Talk.
Update
3 Nov 15:16:07
A further rolling update of all LNSs is expected later in the month.
Started 3 Nov 01:00:00
Closed 3 Nov 12:00:00

2 Nov 22:05:00
Details
Posted: 2 Nov 21:59:48
We're experiences high traffic levels on some of our core routers - we're investigating, but this may be causing some disruption for customers.
Update
2 Nov 22:06:32
Thing are looking back to normal now...
Started 2 Nov 21:45:00
Closed 2 Nov 22:05:00

20 Oct 15:01:04
Details
Posted: 20 Oct 15:01:04

Multiple vulnerabilities have been reported in dnsmasq, the service on the ZyXEL routers which provides a DNSresolver, DHCP functions and router advertisement for IPv6.
A list of these can be found here.

The scope of these is relatively broad, and most attack vectors are local. causing the router to fail DNS/DHCP/RA if exploited (DoS condition), one additional vector includes execution of arbitrary code.
As dnsmasq is tightly integrated into the router, it can't just be turned off, however as a workaround you can change the DNS servers the routers serves in it's DHCP server to minimise potential impact from a local attacker should they perform a DNS request in a way which exploits the DoS conditions. This can be performed by going to the Router Settings page on your control pages, and entering our nameservers 217.169.20.20 and 217.169.20.21 into the IPv4 DNS fields, clicking save, then clicking on the DHCP button at the bottom (for B10Ds only) or clicking on Send ZyXEL configuration (B10As or B10Ds, will wipe existing settings on the router)

An official patch from ZyXEL is estimated to be provided during December 2017 for the VMG1312-B10D routers (Firmware V5.13(AAXA.7)), and January 2018 for the the VMG1312-B10A routers.
An update will be made to this post once firmware updates have been released.

Expected close 01 Feb 2018

16 Oct 14:00:00
Details
Posted: 16 Oct 13:33:49
Texts and emails reporting lines up/down, engineer visits and some other information have been broken over the weekend. This means some delayed messages are being sent out. Sorry for any confusion, it should all be sorted shortly.
Started 16 Oct 13:00:00
Closed 16 Oct 14:00:00
Previously expected 16 Oct 14:00:00

10 Oct 20:03:21
Details
Posted: 26 Apr 10:16:02
We have identified packet loss across our lines at MOSS SIDE that occurs between 8pm to 10pm. We have raised this with BT who suggest that they hope to have this resolved on May 30th. We will update you on completion of this work.
Broadband Users Affected 0.15%
Started 26 Apr 10:13:41 by BT
Closed 10 Oct 20:03:21
Previously expected 30 May (Last Estimated Resolution Time from BT)

10 Oct 19:58:12
Details
Posted: 10 Oct 20:00:14
The "B" LNS restarted for some reason, we are looking in to why but this will mean some customers lost PPP connectivity. Obviously customers connected back again as fast as their router will retry - either to backup LNS or the "B" LNS which rebooted within a few seconds. Sorry for any inconvenience.
Started 10 Oct 19:52:00
Closed 10 Oct 19:58:12

27 Sep 13:15:00
Details
Posted: 27 Sep 13:06:43
At 13:01 we saw a number of broadband lines drop and reconnect. We are investigating the cause.
Update
27 Sep 13:18:20
This affected circuits on our 'H' and 'I' LNSs, customers on LNSs 'A' through to 'G' were unaffected.
Started 27 Sep 13:01:00
Closed 27 Sep 13:15:00

17 Sep 10:10:00
Details
Posted: 17 Sep 09:42:04
Latest from TalkTalk: BT advise their engineer is due on site at 08:40 to investigate, and they are still attempting to source a Fibre Precision Test Officer. Our field engineer has been called out and is en route to site (ETA 08:30).
Update
17 Sep 09:43:18
TalkTalk say affected area codes are: 01481, 01223, 01553, 01480, 01787, 01353 and maybe others. ( Impacted exchanges are Barrow, Buntingford, Bottisham, Burwell, Cambridge, Crafts Hill, Cheveley, Clare, Comberton, Costessey, Cherry Hinton, Cottenham, Dereham, Downham Market, Derdingham, Ely, Fakenham, Fordham Cambs, Feltwell, Fulbourn, Great Chesterford, Girton,Haddenham, Histon, Holt, Halstead, Harston, Kentford, Kings Lynn, Lakenheath, Littleport, Madingley, Melbourne, Mattishall, Norwich North, Rorston, Science Park, Swaffham, Steeple Mordon, Soham, Sawston, Sutton, South Wootton, Swavesey, Teversham, Thaxted, Cambridge Trunk, Trumpington, Terrington St Clements, Tittleshall, Willingham, Waterbeach, Watlington, Watton, Buckden, Crowland, Doddington, Eye, Friday Bridge, Glinton, Huntingdon, Long Sutton, Moulton Chapel, Newton Wisbech, Parson Drove, Papworth St Agnes, Ramsey Hunts, Sawtry, Somersham, St Ives, St Neots, Sutton Bridge, Upwell, Warboys, Werrington, Whittlesey, Woolley, Westwood, Yaxley, Ashwell, Gamlingay and Potton. )
Update
17 Sep 09:43:37
TalkTalk say: Our field engineer and BT field engineer have arrived at site with investigations to the root cause now underway. At this stage Incident Management is unable to issue an ERT until the engineers have completed their diagnostics.
Update
17 Sep 09:55:09
Some lines logged back it at around 09:48
Update
17 Sep 10:10:17
Most are back online now.
Resolution From TalkTalk: Our NOC advised that alarms cleared at 09:45 and service has been restored. Our Network Support has raised a case with Axians (vendor) as there appeared to be an issue between the interface cards in the NGE router and the backplane (which facilitates data flow from the interface cards through the NGE). This incident is resolved and will now be closed with any further root cause with the Problem Management process.
Started 17 Sep 06:20:00
Closed 17 Sep 10:10:00

13 Sep 16:37:14
Details
Posted: 13 Sep 16:17:34

I am pleased to confirm we have now launched "Quota Bonus"

The concept is simple, and applies to Home::1 and SoHo::1 on all levels including terabyte.

You start your billing month with your quota as normal, but get an extra bonus that is half of the unused quota, if any, from the previous month.

This allows people to build up a reserve and allow for occasional higher months without needing top-up.

Thanks to all of the customers for the feedback on my blog posts on this. --Adrian.

P.S. yes, it is sort of cumulative, see examples on http://aa.net.uk/broadband-quota.html

Started 13 Sep 16:15:00

8 Sep 01:00:00
Details
Posted: 7 Sep 23:04:00
Packet loss has been noted to some destinations, routed via LONAP. Our engineers are currently investigating and attempting to work around the loss being observed.
Update
7 Sep 23:23:52
We have disabled all of our LONAP ports for the moment - this reduces our capacity somewhat, but at this time of day the impact to customers is low. We've seen unconfirmed reports that there is some sort of problem with the LONAP peering network, we are still investigating ourselves. (LONAP is a peering exchange in London which connects up lots of ISPs and large internet companies, it's one of the main ways we connect to the rest of the Internet).
Update
7 Sep 23:24:21
LONAP engineers are looking in to this.
Update
7 Sep 23:31:09
We are now not seeing packet loss on the LONAP network - we'll enable our sessions after getting an 'all-clear' update from LONAP staff.
Update
7 Sep 23:39:44
Packet loss on the LONAP network has returned, we still have our sessions down, we're still waiting for the all-clear from LONAP before we enable our sessions again. Customers are on the whole, unaffected by this. There are reports of high latency spikes to certain places, which may or may not be related to what is happening with LONAP at the moment.
Update
8 Sep 06:57:44
We have re-enabled our LONAP sessions.
Resolution The LONAP peering exchange confirm that they had some sort of network problem which was resolved at around 1AM. It's unconfirmed, but the problem looks to be related to some sort of network loop.
Broadband Users Affected 100%
Started 7 Sep 22:42:00 by AA Staff
Closed 8 Sep 01:00:00
Previously expected 8 Sep 03:01:52 (Last Estimated Resolution Time from AAISP)

5 Sep 14:30:00
Details
Posted: 5 Sep 12:01:04
We are seeing very high latency - over 1,000ms on many lines in the East of England. Typically around the Cambridgeshire/Suffolk area. This is affecting BT circuits, TalkTalk circuits are OK. We are investigating further and contacting BT. We suspect this is a failed link within the BT network in the Cambridge area. More details to follow shortly.
Update
5 Sep 12:28:00

Example line graph.
Update
5 Sep 12:35:38
We're currently awaiting a response from BT regarding this.
Update
5 Sep 12:37:16
BT are now actively investigating the fault.
Update
5 Sep 14:04:16
As expected, this is affecting other ISPs who use BT backhaul.
Update
5 Sep 14:23:02
Latest update from BT:- "The Transmission group are investigating further they are carrying out tests on network nodes, As soon as they have identified an issue we will advise you further. We apologies for any inconvenience caused while testing is carried out."
Update
5 Sep 14:34:35
Latency is now back to normal. We will post again when we hear back from BT.
Resolution BT have confirmed that a card in one of their routers was replaced yesterday to resolve this.
Started 5 Sep 11:00:00
Closed 5 Sep 14:30:00

4 Sep 17:23:17
Details
Posted: 4 Sep 17:22:46

We have a number of tariff changes planned, after a lot of interesting comments from my blog post - thank you all.

Some things are simple, and we are able to do sooner rather than later, like the extra 50GB already announced. Some will not be until mid to late October as they depend on other factors. Some may take longer still.

To try and ensure we get improvements as quickly as possible for customers I am updating a news item on our web site with details as we go.

http://aa.net.uk/news-2017-tariffs.html

As you will see, we are testing a change to make top-up on Home::1/SoHo::1 not expire. We have the end of a period (full moon) in two days where we can see if code changes work as expected on a live customer line. If all goes well then later this week we can change the description on the web site and officially launch this change.

Do check that page for updates and new features we are adding as we go.

Update
6 Sep 13:57:18
We have made top-up on Home::1 and SoHo::1 not expire, continuing until you have used it all. This applies to any top-up purchased from now on.
Started 4 Sep 17:19:37

3 Sep 08:14:53
Details
Posted: 3 Sep 08:12:02

We have changed the monthly quota allowances on Home::1 and SoHo::1 today, increasing all of the sub terabyte rates by 50GB per month, without changing prices.

I.e. you now get 200GB for the previous price of 150GB, and 300GB for the previous price of 250GB.

Existing customers have had this additional amount added to their September quota.

Started 3 Sep 08:10:00

29 Aug 13:59:08
Details
Posted: 7 Jul 10:39:42

For the past few years we've been supplying the ZyXEL ZyXEL VMG1312-B10A router. This is being discontinued and we will start supplying its replacement, the ZyXEL VMG1312-B10D (note the subtle difference!)

The new router is smaller than the previous one and has a very similar feature set and web interface to the old one.

We are still working through our configuration process and are updating the Support site with documentation. We are hoping this model to resolve many of the niggles we have with the old one too.

Started 7 Jul 13:12:00

29 Aug 13:00:00
Details
Posted: 17 Jun 15:24:16
We've seen very slight packet loss on a number of TalkTalk connected lines this week in the evenings. This looks to be congestion, it's may show up on our CQM graphs as a few pixels of red at the top of the graph between 7pm and midnight. We have an incident open with TalkTalk. We moved traffic to our Telehouse interconnect on Friday afternoon and Friday evening looked to be better. This may mean that th econgestion is related to TalkTalk in Harbour Exchange, but it's a little too early to tell at the moment. We are monitoring this and will update again after the weekend.
Update
19 Jun 16:49:34

TalkTalk did some work on the Telehouse side of our interconnect on Friday as follows:

"The device AA connect into is a chassis with multiple cards and interfaces creating a virtual switch. The physical interface AA plugged into was changed to another physical interface. We suspect this interface to be faulty as when swapped to another it looks to have resolved the packet loss."

We will be testing both of our interconnects individually over the next couple of days.

Update
20 Jun 10:29:05
TalkTalk are doing some work on our Harbour Exchange side today. Much like the work they did on the Telehouse side, they are moving our port. This will not affect customers though.
Update
28 Jun 20:46:34

Sadly, we are still seeing very low levels of packetloss on some TalkTalk connected circuits in the evenings. We have raised this with TalkTalk today, they have investigated this afternoon and say: "Our Network team have been running packet captures at Telehouse North and replicated the packet loss. We have raised this into our vendor as a priority and are due an update tomorrow."

We'll keep this post updated.

Update
29 Jun 22:12:17

Update from TalkTalk regarding their investigations today:- Our engineering team have been working through this all day with the Vendor. I have nothing substantial for you just yet, I have been told I will receive a summary of today's events this evening but I expect the update to be largely "still under investigation". Either way I will review and fire an update over as soon as I receive it. Our Vendor are committing to a more meaningful update by midday tomorrow as they continue to work this overnight.

Update
1 Jul 09:39:48
Update from TT: Continued investigation with Juniper, additional PFE checks performed. Currently seeing the drops on both VC stacks at THN and Hex. JTAC have requested additional time to investigate the issue. They suspect they have an idea what the problem is, however they need to go through the data captures from today to confirm that it is a complete match. Actions Juniper - Review logs captured today, check with engineering. Some research time required, Juniper hope to have an update by CoB Monday. Discussions with engineering will be taking place during this time.
Update
2 Jul 21:19:57

Here is an example - the loss is quite small on individual lines, but as we are seeing this sort of loss on many circuits and the same time (evenings) it make this more severe. It's only due to to our constant monitoring that this gets picked up.

Update
3 Jul 21:47:31
Today's update from Talktalk: "JTAC [TT's vendor's support] have isolated the issue to one FPC [(Flexible PIC Concentrator] and now need Juniper Engineering to investigate further... unfortunately Engineering are US-based and have a public holiday which will potentially delay progress... Actions: Juniper - Review information by [TalkTalk] engineering – Review PRs - if this is a match to a known issue or it's new. Some research time required, Juniper hope to have an update by Thursday"
Update
7 Jul 08:41:26
Update from TalkTalk yesterday evening: "Investigations have identified a limitation when running a mix mode VC (EX4200’s and EX4550's), the VC cable runs at 16gbps rather than 32gbps (16gbps each way). This is why we are seeing slower than expected speeds between VC’s. Our engineering team are working with the vendor exploring a number of solutions."
Update
17 Jul 14:29:29

Saturday 15th and Sunday 16th evenings were a fair bit worse than previous evenings. On Saturday and Sunday evening we saw higher levels of packet loss (between 1% and 3% on many lines) and we also saw slow single TCP thread speeds much like we saw in April. We did contact TalkTalk over the weekend and this has been blamed on a faulty card that TalkTalk had on Thursday that was replaced but has caused traffic imbalance on this part of the network.

We expect things to improve but we will be closely monitoring this on Monday evening (17th) and will report back on Tuesday.

Update
22 Jul 20:23:24
TalkTalk are planning network hardware changes relating to this in the early hours of 1st August. Details here: https://aastatus.net/2414
Update
1 Aug 10:42:58
TalkTalk called us shortly after 9am to confirm that they had completed the work in Telehouse successfully. We will move traffic over to Telehouse later today and will be reporting back the outcome on this status post over the following days.
Update
3 Aug 11:23:55
TalkTalk confirmed that they have completed the work in Harbour Exchange successfully. Time will tell if these sets of major work have helped with the problems we've been seeing on the TalkTalk network; we will be reporting back the outcome on this status post early next week.
Update
10 Aug 16:39:30
The packetloss issue has been looking better since TalkTalk completed their work. We are still wanting to monitor this for another week or so before closing this incident.
Update
29 Aug 13:56:53
The service has been working well over the past few weeks. We'll close this incident now.
Started 14 Jun 15:00:00
Closed 29 Aug 13:00:00

14 Aug 09:14:59
Details
Posted: 11 Aug 18:44:38
We're needing to restart the 'e.gormless' LNS - this will cause PPP to drop for customers. Update to follow.
Update
11 Aug 18:46:19
Customer on this LNS should be logging back in - (if not already)
Update
11 Aug 19:00:27
There are still some lines left to log back in, but most are back now
Update
11 Aug 19:10:47
Most customers are back now.
Update
13 Aug 12:12:47
This happened again on Sunday morning, and again a restart was needed. The underlying problem is being investigated.
Resolution We have now identified the cause of the issue that impacted both "careless" and "e.gormless". There is a temporary fix in place now, which we expect to hold, and the permanent fix will be deployed on the next rolling update of LNSs.
Started 11 Aug 18:30:00
Closed 14 Aug 09:14:59

13 Jul 18:00:00
[Broadband] TT blip - Closed
Details
Posted: 13 Jul 11:21:37
We are investigating an issue with some TalkTalk lines that disconnected at 10:51 this morning, most have come back but there are about 20 that are still off line. We are chasing TalkTalk business.
Update
13 Jul 11:23:50
Latest update from TT..... We have just had further reports from other reseller are also experiencing mass amount of circuit drops at the similar time. This is currently being investigated by our NOC team and updates to follow after investigation.
Started 13 Jul 10:51:49 by AAISP Pro Active Monitoring Systems
Closed 13 Jul 18:00:00
Previously expected 13 Jul 15:19:49

19 Jul
Details
Posted: 7 Feb 14:32:32

We are seeing issues with IPv6 on a few VDSL cabinets serving our customers. There is no apparent geographical commonality amongst these, as far as we can tell.

Lines pass IPv4 fine, but only intermittently passing IPv6 TCP/UDP for brief amounts of time, usually 4 or so packets, before breaking. Customers have tried BT modem, Asus modem, and our supplied ZyXEL as a modem and router, no difference on any. We also lent them a FireBrick to do some traffic dumps.

Traffic captures at our end and the customer end show that the IPv6 TCP and UDP packets are leaving us but not reaching the customer. ICMP (eg pings) do work.

The first case was reported to us in August 2016, and it has taken a while to get to this point. Until very recently there was only a single reported case. Now that we have four cases we have a bit more information and are able to look at commonalities between them.

Of these circuits, two are serving customers via TalkTalk and two are serving customers via BT backhaul. So this isn't a "carrier network issue", as far as we can make out. The only thing that we can find that is common is that the cabinets are all ECI. (Actually - one of the BT connected customers has migrated to TalkTalk backhaul (still with us, using the same cabinet and phone line etc) and the IPv6 bug has also moved to the new circuit via TalkTalk as the backhaul provider)

We are working with senior TalkTalk engineers to try to perform a traffic capture at the exchange - at the point the traffic leaves TalkTalk equipment and is passed on to Openreach - this will show if the packets are making it that far and will help in pinning down the point at which packets are being lost. Understandably this requires TalkTalk engineers working out of hours to perform this traffic capture and we're currently waiting for when this will happen.

Update
2 Mar 11:14:48
Packet captures on an affected circuit carried out by TalkTalk have confirmed that this issue most likely lies in the Openreach network. Circuits that we have been made aware of are being pursued with both BT and TalkTalk for Openreach to make further investigations into the issue.
If you believe you may be affected please do contact support.
Update
17 Mar 09:44:00
Having had TalkTalk capture the traffic in the exchange, the next step is to capture traffic at the road-side cabinet. This is being progresses with Openreach and we hope this to happen 'soon'.
Update
29 Mar 09:52:52
We've received an update from BT advising that they have been able to replicate the missing IPv6 packets, this is believed to be a bug which they are pursuing with the vendor.

In the mean time they have also identified a fix which they are working to deploy. We're currently awaiting further details regarding this, and will update this post once further details become known.
Update
18 May 16:30:59
We've been informed that the fix for this issue is currently being tested with Openreach's supplier, but should be released to them on the 25th May. Once released to Openreach, they will then perform internal testing of this before deploying it to their network. We haven't been provided with any estimation of dates for the final deployment of this fix yet.
In the interim, we've had all known affected circuits on TalkTalk backhaul have a linecard swap at the cabinet performed as a workaround, which has restored IPv6 on all TT circuits known to be affected by this issue.
BT have come back to us suggesting that they too have a workaround, so we have requested that it is implemented on all known affected BT circuits to restore IPv6 to the customers known to have this issue on BT backhaul.
Resolution A fix was rolled out on the last week of June, re-testing with impacted customers has showed that IPv6 is functioning correctly on their lines again after Openreach have applied this fix.
Broadband Users Affected 0.05%
Started 7 Feb 09:00:00 by AA Staff
Closed 19 Jul

14 Jul 16:48:39
Details
Posted: 14 Jul 10:33:01
We've just seen BT and TT lines drop. We are investigating.
Update
14 Jul 10:57:12
This is similar to yesterday's problem. We have lost BGP connectivity to both our carriers. Over the past fee minutes the BGP sessions have been going up and down, meaning customers are logging in and then out again. Updates to follow shortly.
Update
14 Jul 11:16:46
Sessions are looking a bit more stable now... customer lines are still reconnecting
Update
14 Jul 11:56:08
We have about half DSL lines logged in, but the remaining half are struggling due to what is looking like a Layer 2 issue on our network.
Update
14 Jul 12:23:19
More DSL lines are now back up. If customers are still off, a reboot may help.
Update
14 Jul 12:35:51
A number of TT and BT lines just dropped. They are starting to reconnect now though.
Update
14 Jul 12:52:31
This is still on going - most DSL lines are back, some have been dropping but the network is still unstable. We are continuing to investigate this.
Update
14 Jul 12:55:50
We managed to get a lot of lines up after around an hour, during which there was a lot of flapping. The majority of the rest (some of the talk talk back haul lines) came up, and flapped a bit, at 12:00 and came back properly around 12:40. However, we are still trying to understand the issue, and still have some problems, and we suspect there may be more outages. The problem appears to be something at layer 2 but impacting several sites at once.
Update
14 Jul 14:41:23
We believe these outages are due to a partial failure of one of our core switches. We've moved most services away from this switch and are running diagnostics on it at the moment. We are not expecting these diagnostics to affect other services.
Update
14 Jul 17:00:40
The network has been stable for a good few hours now. One of our 40G Telehouse-to-Harbour Exchange interconnects has been taken down and some devices have been moved off of the suspect switch. We have further work to do in investigating the root cause of this and what we plan to do try to stop this from happening again. We do apologise to our customers for the disruption these two outages have caused and we work on trying to prevent this from happening again.
Started 14 Jul 10:30:00
Closed 14 Jul 16:48:39

13 Jul 21:38:01
Details
Posted: 13 Jul 18:56:13
Multiple circuits have disconnected and reconnected, staff are investigating
Update
13 Jul 19:00:34
Sessions seem to be repeatedly flapping rather than reconnecting - staff are investigating.
Update
13 Jul 20:05:47
We are still working on this, it's a rather nasty outage I'm afraid and is proving difficult to track down.
Update
13 Jul 20:17:42
Lines are re-connecting now...
Update
13 Jul 20:19:16
Apologies for the loss of graphs on a.gormless. We usually assume the worst and that out kit is the cause and tried a reboot of a FireBrick LNS. It did not help, but did clarify the real cause which was cisco switches. Sorry for the time it took to track this one down.
Update
13 Jul 20:19:27
Some line are being forced to reconnect so as to move them to the correct LNS, this will cause a logout/login for some customers...
Update
13 Jul 20:25:52
Lines are still connecting, not all are back, but the number of connected lines is increasing.
Update
13 Jul 20:29:55
We're doing some work which may cause some lines to go offline - we expect line to start reconnecting in 10 minutes time.
Update
13 Jul 20:34:35
We are rebooting stuff to try and find the issue. This is very unusual.
Update
13 Jul 20:42:56
Things are still not stable and lines are still dropping. We're needing to reboot some core network switches as part of our investigations and this is happening at the moment.
Update
13 Jul 20:52:29
Lines are reconnecting once more
Update
13 Jul 21:17:36
Looking stable.
Update
13 Jul 21:23:48
Most lines are back online now, if customers re still not online they a reboot of the router or modem may be required as the session may have got stuck inside the back haul network.
Update
13 Jul 21:41:38

We'll close this incident as lines have been stable for an hour. We'll update the post with further information as to the cause and any action we will be taking to help stop this type of incident from happening again.

We would like to thank our customers for their patience and support this evening. We had many customers in our IRC channel who were in good spirits and supportive to our staff whilst they worked on this incident.

Update
14 Jul 14:42:20
A similar problem occurred on Friday morning, this is covered on the following post: https://aastatus.net/2411
Closed 13 Jul 21:38:01

10 Jul 02:21:59
[Broadband] BT blip - Closed
Details
Posted: 10 Jul 02:16:23
Looks like all lines on BT backhaul blipped at just before 2am. Lines reconnected right away though. Some lines on wrong LNS now so we may move them back - which with show a longer gap in the graphs.
Update
10 Jul 02:22:25
Sessions are all back, and on the right LNS again.
Started 10 Jul 01:59:03
Closed 10 Jul 02:21:59
Previously expected 10 Jul 02:30:00

3 Jun 17:28:30
Details
Posted: 3 Jun 17:06:27
Something definitely not looking right, seems to be intermittent and impacting Internet access.
Update
3 Jun 17:10:34
Looks like a denial of service attack of some sort.
Update
3 Jun 17:17:45
Looks like may be more widespread than just us.
Update
3 Jun 17:23:17
Definitely a denial of service attack, impacted some routers and one of the LNSs. Some graphs lost.
Resolution Target isolated for now.
Started 3 Jun 16:59:05
Closed 3 Jun 17:28:30

8 Jun 10:49:27
Details
Posted: 7 Jun 10:33:00
We are seeing some customers who are still down following a blip within TalkTalk. We currently have no root cause but are investigating.
Update
7 Jun 11:13:21
A small number of lines are still down, however most have now resumed service. We are still communicating with TalkTalk so we can restore service for all affected lines.
Update
7 Jun 11:23:02
Looks like we're seeing another blip affecting many more customers this time. We are still speaking to TalkTalk to determine the cause of this.
Update
7 Jun 11:59:53

TalkTalk have raised an incident with teh following information:

"We have received reports from a number of B2B customers (Wholesale ADSL) who are experiencing a loss of their Broadband services. The impact is believed to approximately 600 lines across 4 or 5 partners. All of the impacted customers would appear to route via Harbour Exchange. Our NOC have completed initial investigations and have passed this to our IP operations team to progress. "

As a result, we'll move TalkTalk traffic away from the Harbour Exchange datacentre to see if it helps. This move will be seamless and will not affect other customers.

Update
7 Jun 12:05:38
Our TalkTalk traffic has now been moved away from HEX89, if There are still a small number of customers offline, if they reboot their router/modem that may force a re-connection and a successful login.
Update
7 Jun 12:37:29
At 12:29 we saw around 80 lines drop, most of these are back online as of 12:37 though. The incident is still open with TalkTalk engineers.
Update
7 Jun 13:19:57
TalkTalk are really not having a good day. We're now seeing packetloss on lines as well as a few more drops. We're going to bring the HEX89 interconnect back up in case that is in any way related, we're also chasing TT on this.
Update
7 Jun 14:37:21
This is still an open incident with TalkTalk, it is affecting other ISPs using TalkTalk as their backhaul. We have chased TalkTalk for an update.
Update
7 Jun 15:37:21

Update from TalkTalk: "Network support have advised that service has been partially restored. Currently Network Support are continuing to re-balance traffic between both LTS’s (HEX & THN). This work is currently being completed manually by our Network support team who ideally need access to RadTools to enable them to balance traffic more efficiently. We are currently however experiencing an outage of RadTools which is being managed under incident 10007687. We will continue to provide updates on the progress as soon as available."

Probably as a result, we are still seeing low levels of packetloss on some TalkTalk lines.

Update
7 Jun 16:49:12
It's looking like the low levels of packetloss stopped at 16:10. Things are looking better.
Update
8 Jun 08:31:43
There are a handful of customers that are still offline, we have sent the list of these circuits to TalkTalk to investigate.
Update
8 Jun 10:26:02

Update from TalkTalk: "We have received reports from a number of B2B customers (Wholesale ADSL & FTTC) who are experiencing authentication issues with their Broadband services. The impact is believed to approximately 100 lines across 2 partners. All of the impacted customers would appear to route via Harbour Exchange. Our NOC have completed initial investigations and have passed this to our Network support team to progress."

We have actaully already taken down our Harbour Exchange interconnect but this has not helped.

Update
8 Jun 10:49:27
Over half of these remaining affected lines logged back in at 2017-06-08 10:38
Update
8 Jun 11:22:39
The remaining customers offline should try rebooting their router/modem and if still not online then please contact Support.
Resolution

From TalkTalk: The root cause of this issue is believed to have been caused by a service request which involved 3 network cards being installed in associated equipment at Harbour exchange. This caused BGP issues on card (10/1). To resolve this Network Support shut down card (10/1) but this did not resolve all issues. This was then raised this to Ericsson who recommended carrying out an XCRP switchover on the LTS. Once the switchover was carried out all subscribers connections dropped on the LTS and the majority switched over to the TeleHouse North LTS. Network support then attempted to rebalance the traffic across both LTS platform however were not able to due to an ongoing system incident impacting Radius Tools. Network support instead added 2 new 10G circuits to the LTS platform to relieve the congestion and resolve any impact. As no further issues have been identified this incident will now be closed and any further RCA investigation will be carried out by problem management.

Regarding the problem with a few circuits not able to establish PPP. the report from TalkTalk is as follows: Network support have advised that they have removed HEX (harbour exchange) from the radius to restore service until a permanent fix can be identified. Network support are liaising with Ericsson in regards to this and investigations are ongoing.

Broadband Users Affected 0.20%
Started 7 Jun 10:05:00
Closed 8 Jun 10:49:27

27 Mar 09:30:00
Details
Posted: 19 Feb 18:35:15
We have seen some cases with degraded performance on some TT lines, and we are investigating. Not a lot to go on yet, but be assured we are working on this and engaging the engineers within TT to address this.
Update
21 Feb 10:13:20

We have completed further tests and we are seeing congestion manifesting itself as slow throughput at peak times (evenings and weekends) on VDSL (FTTC) lines that connect to us through a certain Talk Talk LAC.

This has been reported to senior TalkTalk staff.

To explain further; VDSL circuits are routed from TalkTalk to us via two LACs. We are seeing slow thoughput at peak times on one LAC and not the other.

Update
27 Feb 11:08:58
Very often with congestion it is easy to find the network port or system that is overloaded but so far, sadly, we've not found the cause. A&A staff and customers and TalkTalk network engineers have done a lot of checks and tests on various bits of the backhaul network but we are finding it difficult to locate the cause of the slow throughput. We are all still working on this and will update again tomorrow.
Update
27 Feb 13:31:39
We've been in discussions with other TalkTalk wholesalers who have also reported the same problem to TalkTalk. There does seem to be more of a general problem within the TalkTalk network.
Update
27 Feb 13:32:12
We have had an update from TalkTalk saying that based on multiple reports from ISPs that they are investigating further.
Update
27 Feb 23:21:21
Further tests this evening by A&A staff shows that the throughput is not relating to a specific LAC, but that it looks like something in TalkTalk is limiting single TCP sessions to 7-9M max during peak times. Running single iperf tests results in 7-9M, but running ten at the same time can fill a 70M circuit. We've passed these findings on to TalkTalk.
Update
28 Feb 09:29:56
As expected the same iperf throughput tests are working fine this morning. TT are shaping at peak times. We are pursuing this with senior TalkTalk staff.
Update
28 Feb 11:27:45
TalkTalk are investigating. They have stated that circuits should not be rate limited and that they are not intentionally rate limiting. They are still investigating the cause.
Update
28 Feb 13:14:52
Update from TalkTalk: Investigations are currently underway with our NOC team who are liaising with Juniper to determine the root cause of this incident.
Update
1 Mar 16:38:54
TalkTalk are able to reproduce the throughput problem and investigations are still on going.
Update
2 Mar 16:51:12
Some customers did see better throughput on Wednesday evening, but not everyone. We've done some further testing with TalkTalk today and they continue to work on this.
Update
2 Mar 22:42:27
We've been in touch with the TalkTalk Network team this evening and have been performing further tests (see https://aastatus.net/2363 ). Investigations are still ongoing, but the work this evening has given a slight clue.
Update
3 Mar 14:24:48
During tests yesterday evening we saw slow throughput when using the Telehouse interconnect and fast (normal) throughput over Harbour Exchange interconnect. Therefore, this morning, we disabled our Telehouse North interconnect. We will carry on running tests over the weekend and we welcome customers to do the same. We are expecting throughput to but fast for everyone. We will then liaise with TalkTalk engineers regarding this on Monday.
Update
6 Mar 15:39:33

Tests over the weekend suggest that speeds are good when we only use our Harbour Exchange interconnect.

TalkTalk are moving the interconnect we have at Telehouse to a different port at their side so as to rule out a possible hardware fault.

Update
6 Mar 16:38:28
TalkTalk have moved our THN port and we will be re-testing this evening. This may cause some TalkTalk customers to experience slow (single thread) downloads this evening. See: https://aastatus.net/2364 for the planned work notice.
Update
6 Mar 21:39:55
The testing has been completed, and sadly we still see slow speeds when using the THN interconnect. We are now back to using the Harbour Exchange interconnect where we are seeing fast speeds as usual.
Update
8 Mar 12:30:25
Further testing happening today: Thursday evening https://aastatus.net/2366 This is to try and help narrow down where the problem is occurring.
Update
9 Mar 23:23:13
We've been testing, tis evening, this time with some more customers, so thank you to those who have been assisting. (We'd welcome more customers to be involved - you just need to run an iperf server on IPv4 or IPv6 and let one of our IPs through your firewall - contact Andrew if you're interested). We'll be passing the results on to TalkTalk, and the investigation continues.
Update
10 Mar 15:13:43
Last night we saw some line slow and some line fast, so having extra lines to test against should help in figuring out why this is the case. Quite a few customers have set up iperf server for us and we are now testing 20+ lines. (Still happy to add more). Speed tests are being run three times an hour and we'll collate the results after the weekend and will report back to TalkTalk the findings.
Update
11 Mar 20:10:21
Update
13 Mar 15:22:43

We now have samples of lines which are affected by the slow throughput and those that are not.

Since 9pm Sunday we are using the Harbour Exchange interconnect in to TalkTalk and so all customers should be seeing fast speeds.

This is still being investigated by us and TalkTalk staff. We may do some more testing in the evenings this week and we are continuing to run iperf tests against the customers who have contacted us.
Update
14 Mar 15:59:18

TalkTalk are doing some work this evening and will be reporting back to us tomorrow. We are also going to be carrying out some tests ourselves this evening too.

Our tests will require us to move traffic over to the Telehouse interconnect, which may mean some customers will see slow (single thread) download speeds at times. This will be between 9pm and 11pm

Update
14 Mar 16:45:49
This is from the weekend:

Update
17 Mar 10:42:28
We've stopped the iperf testing for the time being. We will start it back up again once we or TalkTalk have made changes that require testing to see if things are better or not, but at the moment there is no need for the testing as all customers should be seeing fast speeds due to the Telehouse interconnect not being in use. Customers who would like quota top-ups, please do email in.
Update
17 Mar 18:10:41
To help with the investigations, we're also asking for customers with BT connected FTTC/VDSL lines to run iperf so we can test against them too - details on https://support.aa.net.uk/TTiperf Thank you!
Update
20 Mar 12:54:02
Thanks to those who have set up iperf for us to test against. We ran some tests over the weekend whilst swapping back to the Telehouse interconnect, and tested BT and TT circuits for comparison. Results are that around half the TT lines slowed down but the BT circuits were unaffected.

TalkTalk are arranging some further tests to be done with us which will happen Monday or Tuesday evening this week.

Update
22 Mar 09:37:30
We have scheduled testing of our Telehouse interlink with TalkTalk staff for this Thursday evening. This will not affect customers in any way.
Update
22 Mar 09:44:09
In addition to the interconnect testing on Thursday mentioned above, TalkTalk have also asked us to retest DSL circuits to see if they are still slow. We will perform these tests this tonnight, Wednesday evening.

TT have confirmed that they have made a configuration change on the switch at their end in Telehouse - this is the reason for the speed testing this evening.

Update
22 Mar 12:06:50
We'll be running iperf3 tests against our TT and BT volunteers this evening, very 15 minutes from 4pm through to midnight.
Update
22 Mar 17:40:20
We'll be changing over to the Telehouse interconnect between 8pm and 9pm this evening for testing.
Update
23 Mar 10:36:06

Here are the results from last night:

And BT Circuits:

Some of the results are rather up and down, but these lines are in use by customers so we would expect some fluctuations, but it's clear that a number of lines are unaffected and a number are affected.

Here's the interesting part. Since this problem started we have rolled out some extra logging on to our LNSs, this has taken some time as we only update one a day. However, we are now logging the IP address used at our side of L2TP tunnels from TalkTalk. We have eight live LNSs and each one has 16 IP addresses that are used. With this logging we've identified that circuits connecting over tunnels on 'odd' IPs are fast, whilst those on tunnels on 'even' IPs are slow. This points to a LAG issue within TalkTalk, which is what we have suspected from the start but this data should hopefully help TalkTalk with their investigations.

Update
23 Mar 16:27:28
As mentioned above, we have scheduled testing of our Telehouse interlink with TalkTalk staff for this evening. This will not affect customers in any way.
Update
23 Mar 22:28:53

We have been testing the Telehouse interconnect this evening with TalkTalk engineers. This involved a ~80 minute conference call and setting up a very simple test of a server our side plugged in to the switch which is connected to our 10G interconnect, and running iperf3 tests against a laptop on the TalkTalk side.

The test has highlighted a problem at the TalkTalk end with the connection between two of their switches. When plugged in to the second switch we got about 300Mbit/s, but when their laptop was in the switch directly connected to our interconnect we got near full speed or around 900Mb/s.

This has hopefully given them a big clue and they will now involve the switch vendor for further investigations.

Update
23 Mar 23:02:34
TalkTalk have just called us back and have asked us to retest speeds on broadband circuits. We're moving traffic over to the Telehouse interconnect and will test....
Update
23 Mar 23:07:31
Initial reports show that speeds are back to normal! Hooray! We've asked TalkTalk for more details and if this is a temporary or permanent fix.
Update
24 Mar 09:22:13

Results from last night when we changed over to test the Telehouse interlink:

This shows that unlike the previous times, when we changed over to use the Telehouse interconnect at 11PM speeds did not drop.

We will perform hourly iperf tests over the weekend to be sure that this has been fixed.

We're still awaiting details from TalkTalk as to what the fix was and if it is a temporary or permanent fix.

Update
24 Mar 16:40:24
We are running on the Telehouse interconnect and are running hourly iperf3 tests against a number of our customers over the weekend. This will tell us if the speed issues are fixed.
Update
27 Mar 09:37:12

Speed tests against customers over the weekend do not show the peak time slow downs, this confrims that what TalkTalk did on Thursday night has fixed the problem. We are still awaiting the report from TalkTalk regarding this incident.

The graph above shows iperf3 speed test results taken once an hour over the weekend against nearly 30 customers. Although some are a bit spiky we are no longer seeing the drastic reduction in speeds at peak time. The spikyness is due to the lines being used as normal by the customers and so is expected.

Update
28 Mar 10:52:25
We're expecting the report from TalkTalk at the end of this week or early next week (w/b 2017-04-03).
Update
10 Apr 16:43:03
We've not yet had the report from TalkTalk, but we do expect it soon...
Update
4 May 09:16:33
We've had an update saying: "The trigger & root cause of this problem is still un-explained; however investigations are continuing between our IP Operation engineers and vendor".

This testing is planned for 16th May.

Resolution From TT: Planned work took place on the 16th May which appears to have been a success. IP Ops engineers swapped the FPC 5 and a 10 gig module on the ldn-vc1.thn device They also performed a full reload to the entire virtual chassis (as planned). This appears to have resolved the slow speed issues seen by the iperf testing onsite. Prior to this IP ops were seeing consistent slow speeds with egress traffic sourced from FPC5 to any other FPC; therefore they are confident that this has now been fixed. IP Ops have moved A&A's port back to FPC 5 on LDN-vc1.thn.
Started 18 Feb
Closed 27 Mar 09:30:00
Cause TT

17 May 12:00:00
Details
Posted: 26 Apr 11:01:07
We have noticed packetloss between 8pm and 10pm on Tuesday (25th April) evening on a small number of TalkTalk connected lines. This may be related to TalkTalk maintenance. We will review this again tomorrow.
Update
26 Apr 16:41:43
We are seeing packet loss this afternoon on some of these lines too. We are contacting TalkTalk.
Update
26 Apr 16:44:23
Update
26 Apr 17:58:06
We have moved TalkTalk traffic over to our Harbour Exchange interconnect to see if this makes a difference or not to the packet loss that we are seeing...
Update
26 Apr 20:50:41
Moving the traffic made no difference. We've had calls with TalkTalk and they have opened an incident and are investigating further.
Update
26 Apr 20:55:14
The pattern that we are seeing relates to which LAC TT are using to send traffic over to us. TT use two LACs at their end, and lines via one have loss whilst lines via the other have no loss.
Update
26 Apr 21:32:30
Another example, showing the loss this evening:

Update
26 Apr 22:26:50
TalkTalk have updated us with: "An issue has been reported that some Partners are currently experiencing quality of service issues, such as slow speed and package (SIC) loss, with their Broadband service. From initial investigations the NOC engineers have identified congestion to the core network connecting to Telehouse North as being the possible cause. This is impacting Partners across the network and not specific to one region, and the impacted volume cannot be determine at present. Preliminary investigations are underway with our NOC and Network Support engineers to determine the root cause of this network incident. At this stage we are unable to issue an ERT until the engineers have completed further diagnostics."
Update
28 Apr 09:43:43
Despite Talktalk thinking they had fixed this we are still seeing packetloss on these circuits between 8pm and 10pm. It's not as much packetloss as we saw on Wednesday evening, but loss nonetheless. This has been reported back to TalkTalk.
Update
4 May 15:42:04
We are now blocking the two affected Talkalk LACs on new connections, eg a PPP re-connect. This means that it will take a bit longer for a line to re-connect (depending upon the broadband router perhaps a minute or two).

This does mean that lines will not be on the LACs which have evening packetloss. We hope not to have to keep this blocking in place for very long as we hope TalkTalk fix this soon.

Update
5 May 16:48:13
We've decided to not block the LACs that are showing packetloss as it was causing connection problems for a few customers. We have had a telephone call with TalkTalk today, and this issue is being escalated with TalkTalk.
Update
5 May 19:47:37
We've had this update from TalkTalk today:

"I have had confirmation from our NOC that following further investigations by our IP Operations team an potential issue has been identified on our LTS (processes running higher than normal). After working with our vendor it has been recommended a card switch-over should resolve this.

This has been scheduled for 16th May. We will post further details next week.

Update
8 May 09:26:21
Planned work has been scheduled for 16th May for this, details and updates of this work is on https://aastatus.net/2386
Update
5 Jun 11:49:24
The planned work took place on the 16th May which appears to have been a success.
Broadband Users Affected 20%
Started 26 Apr 10:00:00
Closed 17 May 12:00:00

2 Jun 16:44:00
Details
Posted: 2 Jun 12:48:45
We have had several customers notify us that they've having connectivity issues in the Cambridge area, all FTTC customers so far, where TCP packets larger than 1300 bytes appear to be dropped. ICMP appears unaffected.
We are currently in the process of reporting this to BT and will post further updates as they become available.
Update
2 Jun 13:08:24
Proactive have raised a fault, AF-AR-OP-3774655 This has also been discovered to affect FTTP customers, which makes sense as they use the same backbone infrastructure as the FTTC customers.
Update
2 Jun 13:35:22
Several customers are reporting that their lines are now performing as expected after restarting their PPP session, so it may be worth restarting your PPP session and letting us know what happens when you try that.
We're still awaiting an update from proactive.
Resolution We have been advised by BT that a link between Milton Keynes and Peterborough was erroring, and was taken out of service to resolve the issue earlier today.
Broadband Users Affected 0.20%
Started 2 Jun 11:47:00
Closed 2 Jun 16:44:00
Cause BT

17 May 12:30:00
Details
Posted: 17 May 09:10:40
We have identified outages within the North London area affecting multiple exchanges. The affected exchanges are listed as: SHOEBURYNESS,THORPE BAY, CANVEY ISLAND, HADLEIGH – ESSEX, MARINE, NORTH BENFLEET, STANFORD LE HOPE, VANGE, WICKFORD, BLOOMSBURY AKA HOWLAND ST, HOLBORN, PRIMROSE HILL, KINGSLAND GREEN, TOTTENHAM, BOWES PARK, PALMERS GREEN, WALTHAM CROSS, WINCHMORE HILL, EDMONTON, NEW SOUTHGATE, EPPING, HAINAULT, ILFORD NORTH, ROMFORD, UPMINSTER, NORTH WEALD, STAMFORD HILL, DAGENHAM, ILFORD CENTRAL, GOODMAYES, STRATFORD, HIGHAMS PARK, LEYTONSTONE, WALTHAMSTOW, CHINGFORD, KENTISH TOWN and MUSWELL HILL. No root cause has been identified. We will update this status page as the updates become available from our supplier.
Update
17 May 09:30:01
Affected Customers went offline at 02:12 this morning. Further information: These exchanges are off line due to 20 tubes of fibre being damaged by the install of a retail advertising board on the A118 Southern [South?] Kings Rd. Notifications from TalkTalk were expecting service to be restored by 9am, but due to the nature of the fibre break it may well take longer to fix.
Update
17 May 10:31:29
Update from TalkTalk: Virgin media have advised that work to restore service is ongoing but due to the extent of the damage this is taking longer than expected. In parallel our [TalkTalk] NOC are investigating if the Total Loss traffic can be re-routed. We will provide a further update as soon as more information is available.
Update
17 May 10:55:56
From TalkTalk: Virgin Media have advised restoration work has completed on the majority of the damaged fibre, our NOC team have also confirmed a number of exchanges are now up and back in service. The exchanges that are now back in service are Muswell Hill, Ingrebourne, Loughton and Bowes Park.
Update
17 May 11:16:28
From TalkTalk: Our NOC team have advised a number of exchanges are now in service. These are Muswell Hill, Bowes Park, Loughton, Ingrebourne, Bowes Park, Chingford, Highams Park, Leytonstone, Stratford and Upton Park.
Update
17 May 11:30:54
That said, we are still seeing lines on exchanges mentioned above as being offline....
Update
17 May 12:11:20
No further updates as yet.
Resolution It looks like most, if not all, of our affected lines are now back online. Update from TalkTalk: Virgin Media have advised 5 of the 8 impacted fibre tubes have been successfully spliced and their engineers are still on site restoring service to the remaining cables
Started 17 May 01:54:00 by AA Staff
Closed 17 May 12:30:00

4 May 18:00:00
Details
Posted: 4 May 16:53:39
Some TT lines blipped at 16:34 and 16:46. It appears that the lines have recovered. We have reported this to TT.
Update
5 May 08:48:41
This was caused by an incident in the TalkTalk network. This is from TalkTalk: "...Network support have advised that the problem was caused by the card failure which has now been taken offline..."
Started 4 May 16:36:27 by AAISP automated checking
Closed 4 May 18:00:00
Cause TT

17 May 09:10:43
Details
Posted: 22 Apr 11:12:14

We are making some major upgrades to the way we do notifications to customers for orders, faults, etc.

One of the first things to change will be the up/down notifications we send. These can be tweets, texts or emails. Part of the work will be changing the options you have for controlling these.

Over the coming weeks we expect to add new settings, and remove old settings over time. We are aiming to try and mirror most of the existing functionality, in particular the sending of tweets or texts for unexpected line drops for individual lines.

You will also start to see options to load a PGP public key for emailed notifications.

Over coming months we expect to move more and more of our systems over to the new process, including order tracking and engineer appointments, etc.

The end result should be more flexible, and consistent, notifications.

Update
23 Apr 17:54:32

We are mostly ready to switch over to the new system - probably happening on Monday. The wording of the messages will change slightly with the new system. There are already more options on the control pages, and once we have switched over these will replace the old settings.

Once done, we will start using the new system for more and more aspects of the control pages, ordering, and faults, over the coming weeks.

Update
24 Apr 14:23:06
We have switched the line up/down messages to the new KCI system. Please do let us know if you have any concerns or comments.
Update
24 Apr 16:17:34
Customers can now paste a PGP public key in to the control pages login page.
Update
25 Apr 16:02:39
After a few comments we have made sure the postcode and login is shown in the line/up down messages. The new system seems to be working well, and we are ready to start extending it to more messages soon.
Started 23 Apr
Closed 17 May 09:10:43
Previously expected 1 Jun

22 Apr 11:13:59
Details
Posted: 2 Feb 21:19:15
http://www.euronews.com/2017/01/27/adrian-kennard-challenging-surveillance

21 Apr 13:07:49
Details
Posted: 21 Apr 09:59:57
At 9:30 we saw a number of TalkTalk connected circuits drop and reconnect. We're investigating, but seems like a TalkTalk backhaul issue

Update
21 Apr 11:24:54
Most lines logged back in very quickly. A few are still down. It seems TalkTalk had some sort if incident at the Telehouse Harbour Exchange datacentre, we're expecting further information shortly.
Update
21 Apr 12:54:00
TalkTalk have some sort of outage in their Harbour Exchange datacentre. As we have an interconnect in both Telehouse and Harbour Exchange the traffic has moved over to Telehouse. There are a very small number of customers (<10) who are still offline, they may just need a reboot of their router or modem, but we are contacting them individually.
Update
21 Apr 13:08:47
TalkTalk say: Root cause analysis conducted by the NOC and our Network Support team has identified that this incident was caused by a crashed routing card for the LTS. The card was reloaded by our Network Support team and full service has now been restored.
Resolution Any customer still offline, please reboot your router/modem and then contact Support if still off.
Started 21 Apr 09:30:50
Closed 21 Apr 13:07:49

14 Mar 21:10:00
Details
Posted: 14 Mar 21:05:28
Looks like we just had some sort of blip affecting broadband customers. We're investigating.
Resolution This was a LNS crash, and so affected customers on the "i" LNS. The cause is being investigated, but preliminary investigations show that it's probably a problem that is fixed in software that is scheduled to be loaded on to this LNS in a couple of days time as part of the rolling software update that we're performing at the moment.
Broadband Users Affected 12%
Started 14 Mar 21:00:57
Closed 14 Mar 21:10:00

6 Mar 21:37:45
Details
Posted: 6 Mar 16:41:32
As part of the slow throughput problem described in https://aastatus.net/2358 we will be performing further tests this evening. This will involve moving TalkTalk traffic to the interconnect which we believe is slow. Customers may see poor speeds this evening during the times that we carry out tests. The tests are expected to last less than 30 minutes between 8 and 10 pm.
Resolution This work has been completed.
Started 6 Mar 20:00:00
Closed 6 Mar 21:37:45

2 Mar 22:10:44
Details
Posted: 2 Mar 21:48:39
Relating to https://aastatus.net/2358 we are undergoing currently in an emergency at-risk period as we perform some tests along side TalkTalk staff. We don't expect any problems, but this work involves re-routing TalkTalk traffic within our network. This work is happening now. Sorry for the no notice.
Update
2 Mar 21:53:05
We have successfully and cleanly moved all TalkTalk traffic off our THN interconnect and on to our HEX Interconnect. (Usually we use both all the time, but for this testing we are forcing traffic through the HEX side)
Update
2 Mar 21:55:52
We're bringing back routing across both links now...
Update
2 Mar 22:03:40
We are now moving traffic to our THN interconnect.
Resolution We're now back to using both the TalkTalk links. Tests completed.
Started 2 Mar 21:46:17
Closed 2 Mar 22:10:44

16 Feb 15:00:00
Details
Posted: 16 Feb 16:00:49
We have spotted some odd latency that was affecting two of our LNSs (A and B gormless). These were also visible, as you would expect, on the graphs shown for people's lines.
Resolution We believe we have addressed the issue now, sorry for any inconvenience.
Started 15 Feb 02:00:00
Closed 16 Feb 15:00:00
Previously expected 16 Feb 15:00:00

13 Feb 10:02:12
Details
Posted: 13 Feb 10:00:36
We just had an LNS blip - this would have caused some customers to drop PPP and reconnect.
Resolution There have been a few LNS blips recently. However, we do know the cause and have a software update to roll out which will fix the problem.
Started 13 Feb 09:56:00
Closed 13 Feb 10:02:12

4 Feb 09:32:03
Details
Posted: 4 Feb 09:14:11
We had an LNS reset and lines will have re-connected for some customers. We're investigating the cause.
Resolution We have found the cause, and expect a permanent fix to be deployed on next round of LNS upgrades.
Broadband Users Affected 12%
Started 4 Feb 09:12:00
Closed 4 Feb 09:32:03

31 Jan 16:29:00
Details
Posted: 31 Jan 16:24:03
Customers on one of our LNSs just lost their connection and would have logged back in again shortly after. We're investigating the cause
Update
31 Jan 16:41:32
Customers are back online. The CQM graphs for the day would have been lost for these lines. We do apologise for the inconvenience this caused.
Broadband Users Affected 12%
Started 31 Jan 16:16:00
Closed 31 Jan 16:29:00