Order posts by limited to posts

8 Apr 16:58:41
8 Apr 16:58:41
Some lines on the BT LEITH exchange have gone down. BT are aware and are investigating at the moment.
Started 8 Apr 16:30:20 by Customer report
Update was expected 8 Apr 17:40:20

3 Apr 15:57:14
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.

04 Nov 2013 16:52:49
We have been working on getting more specific information regarding this, we hope to post an update tomorrow.
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.
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.
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.
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.
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.

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.
27 Nov 2013 10:10:13
We have also had reports from someone outside of AAISP reproducing this problem.
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.
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
13 Jan 14:09:08
We are still chasing this with BT.
3 Apr 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.
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.
Started 25 Oct 2013

22 Mar 07:36:41
22 Mar 07:36:41
We have started to see yet more congestion on BT lines last night. This looks again a bit like a link aggregation issue (where one leg of a multiple link trunk within BT is full). The patten is not as obvious this time. Looking at the history we can see that some of the affected lines have had slight loss in the evenings. We did not spot this with our tools because of the rather odd pattern. Obviously we are trying to get this sorted with BT, but we are pleased to confirm that BT are actually providing more data now that shows where each circuit will use network components within their network. We plan to integrate this soon so that we can correlate some of these newer congestion issues and point BT in the right direction more quickly.
Started 21 Mar 18:00:00

21 Mar 10:19:24
11 Mar 10:11:55
We are seeing multiple exchanges with packet loss over BT wholesale. We are chasing BT on this and will update as and when we have updates. GOODMAYES CANONBURY HAINAULT SOUTHWARK LOUGHTON HARLOW NINE ELMS UPPER HOLLOWAY ABERDEEN DENBURN HAMPTON INGREBOURNE COVENTRY 21CN-BRAS-RED6-SF
14 Mar 12:49:28
This has now been escalated to the next level for further investigation.
17 Mar 15:42:38
BT are now raising faults on each Individual exchange.
21 Mar 10:19:24
Below are the exchanges/RAS which has been fixed by capacity upgrades. We are hoping for the remanding four exchanges to be fixed in the next few days.
21 Mar 15:52:45
COVENTRY should be resolved later this evening when a new link is installed between Nottingham and Derby. CANONBURY is waiting for CVLAN moves that begin 19/03/2014 and will be competed 01/04/2014.
25 Mar 10:09:23
CANONBURY - Planned Engineering works have taken place on 19.3.14, and there are three more planned 25.3.14 , 26.3.14 and 1.4.14.
COVENTRY - Is now fixed
NINE ELMS and UPPER HOLLOWAY- Still suffering from packet loss and BT are investigating further.
2 Apr 15:27:11
BT are still investigating congestion on Canonbury, Nine Elms and Upper Holloway.
Broadband Users Affected 1%
Started 9 Mar 10:08:25 by AAISP Pro Active Monitoring Systems

20 Mar 11:10:57
17 Feb 20:13:09
We are seeing packet loss at peak times on some lines on the Crouch End exchange. It's a small number of customers, and it looks like a congested SVLAN. This has been reported to BT.
18 Feb 10:52:26
Initially BT were unable to see any problem, their monitoring was not showing any congestion and they wanted us to report individual line faults rather than this being dealt as a specific BT network problem. However we have spoken to another ISP who confirms the problem. BT have now opened an Incident and will be investigating.
18 Feb 11:12:47
We have passed all our circuit details and graphs to proactive to investigate.
18 Feb 16:31:17
TSO will investigate overnight
20 Feb 10:15:02
No updates from TSO, proactive are chasing.
27 Feb 13:24:38
There is still congestion, we are chasing BT again.
28 Feb 09:34:50
Appears the issue is on the MSE router. Lines connected to the MSE are due to be migrated on 21st March however BT are hoping to get this done by 21th March.
Broadband Users Affected 0.10%
Started 17 Feb 20:10:29

3 Apr 12:26:40
25 Mar 09:55:20

We are seeing customer routers being attacked this morning, which is causing them to drop. This was previously reported in the status post http://status.aa.net.uk/1877 where we saw that the attacks were affecting ZyXEL routers, as well as other makes.

Since that post we have updated the configuration of customer ZyXEL routers, where possible and these are no longer being affected. However, these attacks are affecting other types of routers.

We suggest that customers with lines that are dropping to check their router configuration and disable access to the router's web interface from the internet, or at least to change the the port used (eg one in the range of 1024-65535)

Please speak to Support for more information.

28 Mar 10:13:13
This is happening again, do speak to suport if you need help changing the web interface settings.
Customers with ZyXELs can change the port from the control pages.
Started 25 Mar 09:00:40
Closed 3 Apr 12:26:40

1 Apr 10:00:00
1 Apr 12:13:31
Some TalkTalk connected lines dropped at around 09:50 and reconnected a few minutes after. It looks like a connectivity problem between us and TalkTalk on one of our connections to them. We are investigating further.
Started 1 Apr 09:50:00
Closed 1 Apr 10:00:00

31 Mar 15:03:25
31 Mar 09:40:40
Some TalkTalk line diagnostics (Signal graphs and line tests) as available from the Control Pages are not working at the moment. This is being looked in to.
31 Mar 15:03:17
This is resolved. The TalkTalk side appears of have a bug relating to timezones.
Resolution This is resolved. The TalkTalk side appears of have a bug relating to timezones.
Started 31 Mar 09:00:00
Closed 31 Mar 15:03:25

20 Mar 11:17:21
20 Mar 08:38:52
Customers will be seeing what looks like 'duplicated' usage reporting on the control for last night and this morning. This has been caused by a database migration that is taking longer than expected. The usage 'duplication' has been caused by usage reports being missed and so on subsequent hours the usage has been spread equally across missed hours.
This means that overall the usage reporting will be correct, but an individual hour will be incorrect.
This has also affected a few other related things such as the Line Colour states.
20 Mar 11:17:55
Usage reporting is now back to normal.
Started 19 Mar 18:00:00
Closed 20 Mar 11:17:21

2 Mar 11:33:29
1 Mar 04:24:02
Lines: 100% 21CN-REGION-GI-B dropped at 2014-03-01 04:22:17
We have advised BT
This is likely to have affected multiple internet providers using BT
1 Mar 04:25:06
Lines: 100% 21CN-REGION-GI-B dropped again at 2014-03-01 04:23:21.
Broadband Users Affected 2%
Started 1 Mar 04:22:17 by AAISP automated checking
Closed 2 Mar 11:33:29
Cause BT

18 Mar 11:32:53
18 Mar 11:32:53
We have removed the 'Services' hyperlink from our Accounts (billing) system that logs you into Clueless directly.
The alternative is for staff to set your '@a' login to be a Group login. This will then mean that your @a login will be able to see all services on your billing account.
Do email in if you'd like this set up.
Started 18 Mar 09:00:00

11 Mar 09:32:42
6 Mar 13:07:51

We have had a small number of reports from customers who have had the DNS settings on their routers altered. The IPs we are seeing set are and (there may be others)

This type of attack is called Pharming. In short, it means that any internet traffic could be redirected to servers controlled by the attacker.

There is more information about pharming on the following pages:

At the moment we are logging when customers try to accesses these IP addresses and we are then contacting the customers to make them aware.

To solve the problem we are suggesting that customers replace the router or speak to their local IT support.

6 Mar 13:33:10
Changing the DNS settings back to auto, changing the administrator password and disabling WAN side access to the router may also prevent this from happening again.
6 Mar 13:48:14
Also reported here: http://www.pcworld.com/article/2104380/
Resolution We have contacted the few affected customers.
Started 6 Mar 09:00:00
Closed 11 Mar 09:32:42

7 Mar 15:08:45
7 Mar 15:10:59
Some broadbands lined blipped at 15:05. This was a result of one of our LNSs restarting. Lines are back online and we'll investigate the cause
Started 7 Mar 15:03:00
Closed 7 Mar 15:08:45

4 Mar 14:30:58
4 Mar 14:30:58

We are pleased to confirm that we are extending the links to BT for broadband to a third gigabit hostlink. This means we will actually have six gigabit fibres to them allowing lots of headroom and redundancy. This should be seamless to customers but the LNSs known as "A", "B", "C", and "D" will have a new "E" and "F" added and we will run 5 of the 6 LNSs as "live" and one backup. We also have multiple gigabit links in to Talk Talk.

This will happen over the next few months and have planned work "at risk" announcements as necessary.

We are actually growing quite well now, and a lot of this has been put down to Baroness Howe mentioning us in The House of Lords recently. I'd really like to thank her for her support, even if unintentional. (see http://revk.www.me.uk/2014/01/mentioned-in-house-of-lords.html)

We have even put another person in to the sales team to handle the extra load.

Started 4 Mar 14:00:00

3 Mar 13:31:25
17 Jan 16:13:23
It seems that BE/Sky are informing their customers that they can no longer have their public blocks of IPs on their service. As a one off special offer, from now until the end of February March if an ex BE customer migrates to our Home::1 tariff then we can include a /30, /29 or /28 block of IPv4 in additional to the usual IPv6 blocks, for no extra cost.
Information about Home::1 is here: http://aa.net.uk/broadband-home1.html Do mention this offer when ordering.
Do see our page about what we do when we run out of IPv4 though: http://aa.net.uk/kb-broadband-ipv6-plans.html
3 Mar 13:30:56
Offer continued until the end of March.
Started 17 Jan 16:00:00

27 Feb 20:40:00
27 Feb 20:29:14
We are seeing some TT lines dropping and a routing problem.
27 Feb 20:39:20
Things are ok now, we're investigating. This looks to have affected some routing for broadband customers and caused some TT lines to drop.
Resolution We are not entirely sure what caused this, however we do believe it to be related to BGP flapping. This also looks to have affected other ISPs and networks too.
Started 27 Feb 20:18:00
Closed 27 Feb 20:40:00

16 Feb 17:59:00
16 Feb 18:12:15
All lines reconnected right away as per normal backup systems, but graphs on the "B" LNS have lost history before the reset. The exact cause is not obvious yet, but at the same time there is yet another of these quite regular attacks on ZyXEL routers which adds to confusion. As advised on another status post there are changes to ZyXEL router config planned to address the issue.
Broadband Users Affected 33.33%
Started 16 Feb 17:58:00
Closed 16 Feb 17:59:00

24 Feb 12:00:00
11 Jan 08:42:32
Since around 2am, as well as a short burst last night around 19:45, we have seen some issues with some lines. This appears to be specific to certain types of router being used on the lines. We are still investigating this.
11 Jan 10:53:53
At the moment, we have managed to identify at least some of the traffic and the affected routers and block it temporarily. We'll be able to provide some more specific advice on the issue and contact affected customers in due course.
13 Jan 14:07:56
We blocked a further IP this morning.
15 Jan 08:17:47
The issue is related to specific routers, and is affecting many ISPs. In our case it is almost entirely zyxel routers that are affected. It appears to be some sort of widespread and ongoing syn flood attack that is causing routers to crash and resulting in loss of sync. We are operating some source IP blocking temporarily to address these issues for the time being, and will have a simple button on our control pages to reconfigure zyxel routers for affected customers shortly.
7 Feb 10:24:07
Last night and this morning there was another flood of traffic causing ZyXELs to restart. We suggest changing the web port to something other than 80, details can be found here: http://wiki.aa.org.uk/Router_-_ZyXEL_P660R-D1#Closing_WAN_HTTP
13 Feb 10:44:41
We will be contacting ZyXEL customers by email over the next few days regarding these problems. Before that though, to verify our records of the router type, we will be performing a 'scan' of customer's WAN IP addresses. This scan will involve downloading the index page from the WAN address.
20 Feb 21:34:54
Customers with ZyXELs online have been contacted this week regarding this issue.
24 Feb 11:17:13
As per email to affected customers, we are updating the http port on ZyXEL routers today - Customers will be emailed as their router is updated.
Resolution Affected customers have been notified, tools in place on the Control Pages for customers to manage the http port and where appropriate ZyXEL routers have had their http port and WAN settings changed.
Broadband Users Affected 5%
Started 11 Jan 02:00:00
Closed 24 Feb 12:00:00

22 Feb 08:00:00
22 Feb 07:56:22
There seems to have been something going on between 2am and 3am. We even had some incidents in BT, but whatever was going on managed to cause an unexpected restart of on of our LNS ("B") at just after 3am. So graphs before then are lost. At 7:55 lines that ended up on the "D" LNS were moved back to the "B" LNS causing a PPP restart.
Broadband Users Affected 33.33%
Started 22 Feb 03:00:00
Closed 22 Feb 08:00:00
Previously expected 22 Feb 08:00:00

20 Feb 18:18:00
20 Feb 09:20:19
We are seeing some lines unable to log in since a blip at 02:49. We are contacting BT. These lines are in sync, but PPP is failing. It looks like a number of BT RASs are affected, including 21CN-BRAS-RED9-GI-B and 21CN-BRAS-RED1-NT-B.
20 Feb 09:31:18
BT were already aware of the problem and are investigating.
20 Feb 12:23:12
These lines are still down, we are chasing BT.
20 Feb 13:21:20
BT believed this issue had been fixed. We have supplied them with all of our circuits that are down. This is being supplied to TSO and we should have an update in the next hour.
20 Feb 14:26:44
A new incident has been raised as BT thought the issue was fixed.
20 Feb 14:27:56
The issue is apparently still being diagnosed.
20 Feb 21:17:48
BT fixed this at 18:18 this evening.
20 Feb 21:34:04
BT say:
BT apologises for the problems experienced today by WMBC customers and are pleased to advise the issue has been fully resolved following the back out of a planned work completed overnight. BT is aware and understands the fault which occurred and have engaged vendor support to commence urgent investigations to identify the root cause.
The BT Technical Services teams have monitored the network since the corrective actions taken at 18:04 and have confirmed the network has remained stable.
Broadband Users Affected 0.20%
Started 20 Feb 03:49:00
Closed 20 Feb 18:18:00

20 Feb 10:00:00
20 Feb 10:24:43
In addition to https://status.aa.net.uk/1891 there is a UK wide problem with lines logging in. This is affecting other ISPs, and affecting a small number of lines. BT are already aware.
20 Feb 11:07:55
BT are saying this is now fixed. We saw affected lines come back online just after 10am. BT say about half of the UK 21CN WBC lines were affected, however, we only saw a few dozen lines affected.
Started 20 Feb 09:00:00
Closed 20 Feb 10:00:00

1 Feb 09:00:00
1 Feb 03:38:03
Lines: 100% 21CN-REGION-PR dropped at 2014-02-01 03:36:28
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 1%
Started 1 Feb 03:36:28 by AAISP automated checking
Closed 1 Feb 09:00:00
Cause BT

6 Feb 10:00:00
6 Feb 02:07:02
Lines: 100% 21CN-REGION-DY dropped at 2014-02-06 02:05:49
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 1%
Started 6 Feb 02:05:49 by AAISP automated checking
Closed 6 Feb 10:00:00
Cause BT

11 Feb 22:27:34
3 Feb 16:19:38

We have a fault open with BT regarding the Harvington Exchange. We are seeing packet loss, typically between 8am and 2am, and getting up to 20% at peak times in the evening.

BT have already tried resetting the line card, but this has not worked.

BT are still investigating.

3 Feb 16:22:45
Example graph:
3 Feb 20:34:34
This has been escalated within BT. Other ISPs are seeing a similar issue. Currently, BT's 'Technical Services' are investigating the problem.
5 Feb 10:16:58

BT have worked at the exchange early hours of this morning to try and resolve the issue. We will have to wait until around 3pm today to see if the heavy packet loss has been fixed.

The details from BT are as follows: "The technical team have worked all night on this issue. An engineer was sent to the exchange in the early hours of this morning and has reseated several IML cables in the network to see if this alleviates the issue. Ping testing has been carried out extensively since the reseats and where there was small packet loss seen prior to the reseat these are now proving to be totally clear."

5 Feb 16:43:59
Looks like the amount of loss is increasing. BT are still investigating.
6 Feb 11:30:34
From BT: Will get this info back over now and ensure tech services are involved to get to the bottom of this issue as agree this is really frustrating that we cannot find the route cause here
7 Feb 09:06:05
Chasing BT for an update
7 Feb 09:56:20
The controller card was reset rather than changed at 02:56am this morning and TSO are waiting on confirmation now if this has made a difference.
10 Feb 09:22:15
BT's efforts over the weekend has not fixed the problem. We will be chasing BT again.
10 Feb 10:01:42
BT are looking to see if it is possible to move our affected lines on to a different SVLAN. (in short, a different link out of the Exchange). We'll update this post when we get an update from BT.
10 Feb 17:00:06
BT are planning to move the lines to a different SVLAN, we're not sure when this will be done yet though. We'll update again when we have further information.
11 Feb 22:28:06
BT have moved the lines to a different SVLAN, and the packet loss problem has gone away.
Started 21 Jan 09:00:00
Closed 11 Feb 22:27:34

4 Feb 16:00:00
3 Feb 14:45:01

One of our authoritive DNS servers, secondary-dns.co.uk, has died. We are carrying out an emergency migration on to new hardware.

DNS services are still running, albeit only on the Primary Name server. This time period is considered 'at risk'.

The new server should be up and running in the next hour or so.

3 Feb 22:09:46
The replacement server is serving zones correctly, but customers who use secondary-dns.co.uk as a secondary to their own nameserver may not have their zones served yet. The reason is that the backup of zone files that we slave for customers is out of date. Rather than serve potentially incorrect records, we're simply not serving those zones but this means customers who use secondary-dns.co.uk as a secondary to their own nameserver should send it a notify to trigger a zone transfer. This does not affect domains for which we provide primary DNS.
Started 3 Feb 14:40:41
Closed 4 Feb 16:00:00

27 Jan 09:52:29
27 Jan 09:52:29

We've added a new feature to the Control Pages for customers with BT Lines.

The feature is detailed on our wiki here: http://wiki.aa.org.uk/Automatic_Line_Testing

In short, the feature allows ADSL, FTTC and FTTP customers to run automatic line tests. Tests can be run when the line logs in or drops out, and can be run at hourly or daily intervals.

The feature is aimed at helping to diagnose faults, and has been available to staff and we're now making it available to customers.

Started 27 Jan 09:30:00 by AAISP Staff

21 Jan 12:59:59
21 Jan 09:44:47
As of 8:30 this morning most 20CN lines connected to a Sheffield RAS have either been dropping or showing packet loss. We are reporting this to BT at the moment.
21 Jan 10:45:51
BT Engineer on the way to site.
21 Jan 11:07:59
Example graph:
21 Jan 12:58:09
Lines are looking better now.
21 Jan 12:58:22
Lines are looking stable again. No news yet from BT.
21 Jan 13:00:23
BT have reset a card, to resolve the issue.
Resolution Card reset.
Started 21 Jan 09:43:03 by AAISP Pro Active Monitoring Systems
Closed 21 Jan 12:59:59

11 Jan 10:20:45
02 Nov 2013 08:37:13
There may be a momentary blip this morning as some routers are upgraded.
11 Jan 10:20:45
Started again around 10:00, we are getting some dumps.
Started 02 Nov 2013 08:00:00
Previously expected 02 Nov 2013 09:00:00

8 Jan 10:20:00
8 Jan 10:13:35
We are seeing a small number of lines flapping (dropping and reconnecting).
We are investigating.
8 Jan 10:30:20
The dropping has stopped for the moment, lines are back to normal.
Started 8 Jan 09:49:00
Closed 8 Jan 10:20:00

27 Dec 2013 19:50:00
27 Dec 2013 14:58:36
We're seeing some issues to some of BTs BRASs. It looks like most of those in Slough (the BRASs ending -SL).
27 Dec 2013 16:11:03
BT are investigating.
27 Dec 2013 17:46:20
Graphs look like this:
27 Dec 2013 18:18:33
BT have an incident open for this fault, and are investigating.
27 Dec 2013 21:10:13
Lines cleared up at about 19:50. Looking back to normal now. No word from BT yet though.
27 Dec 2013 21:45:39
Lines now looking normal:
Broadband Users Affected 5%
Started 27 Dec 2013 14:38:00
Closed 27 Dec 2013 19:50:00

27 Dec 2013 16:11:38
12 Dec 2013 04:25:03
Lines: 100% 21CN-REGION-NT-B dropped at 2013-12-12 04:23:00
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 1%
Started 12 Dec 2013 04:23:00 by AAISP automated checking
Closed 27 Dec 2013 16:11:38
Cause BT

27 Dec 2013 16:11:29
13 Dec 2013 22:36:02
Lines: 100% 21CN-BRAS-RED9-L-FAR-MONUMENT dropped at 2013-12-13 22:34:19
We have advised BT
This is likely to have affected multiple internet providers using BT
14 Dec 2013 03:29:02
Lines: 100% 21CN-BRAS-RED9-L-FAR-MONUMENT dropped again at 2013-12-14 03:27:17.
Started 13 Dec 2013 22:34:19 by AAISP automated checking
Closed 27 Dec 2013 16:11:29
Cause BT

27 Dec 2013 16:11:15
26 Dec 2013 04:41:03
Lines: 50% 21CN-REGION-L-FAR and 100% 21CN-BRAS-RED4-L-FAR-MOORGATE dropped at 2013-12-26 04:39:59
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 2%
Started 26 Dec 2013 04:39:59 by AAISP automated checking
Closed 27 Dec 2013 16:11:15
Cause BT

20 Nov 2013 06:28:33
20 Nov 2013 06:25:03
Lines: 100% 21CN-REGION-21CN-BRAS-RED10-GI-B and 100% 21CN-REGION-21CN-BRAS-RED11-GI-B and 100% 21CN-REGION-21CN-BRAS-RED12-GI-B and 100% 21CN-REGION-21CN-BRAS-RED13-GI-B and 100% 21CN-REGION-GI-B dropped at 2013-11-20 06:23:33
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 4%
Started 20 Nov 2013 06:23:33 by AAISP automated checking
Closed 20 Nov 2013 06:28:33
Cause BT

27 Nov 2013 05:10:33
27 Nov 2013 05:07:06
Lines: 100% 21CN-REGION-21CN-BRAS-RED10-WV and 98% 21CN-REGION-WV dropped at 2013-11-27 05:05:33
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 1%
Started 27 Nov 2013 05:05:33 by AAISP automated checking
Closed 27 Nov 2013 05:10:33
Cause BT

27 Nov 2013 03:18:05
27 Nov 2013 03:15:02
Lines: 100% 21CN-REGION-21CN-BRAS-RED10-WV and 100% 21CN-REGION-WV dropped at 2013-11-27 03:13:05
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 1%
Started 27 Nov 2013 03:13:05 by AAISP automated checking
Closed 27 Nov 2013 03:18:05
Cause BT

19 Nov 2013 23:24:45
19 Nov 2013 23:21:03
Lines: 94% 21CN-REGION-21CN-BRAS-RED10-WV and 100% 21CN-REGION-WV dropped at 2013-11-19 23:19:45
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 1%
Started 19 Nov 2013 23:19:45 by AAISP automated checking
Closed 19 Nov 2013 23:24:45
Cause BT

28 Nov 2013 19:30:34
28 Nov 2013 19:27:02
Lines: 100% 21CN-REGION-CF-C dropped at 2013-11-28 19:25:34
We have advised BT
This is likely to have affected multiple internet providers using BT
Broadband Users Affected 2%
Started 28 Nov 2013 19:25:34 by AAISP automated checking
Closed 28 Nov 2013 19:30:34
Cause BT

19 Nov 2013 23:22:00
19 Nov 2013 21:51:40
It looks like some lines on the Wolverhampton BRAS are showing significant problems. BT have issued an incident report IMT45679/13 but there are no further details at this time.
Resolution Closure Details: Service was restored at 23:22 when redundancy switch over was performed to move the service to standby path. Service stability have been observed. BT regrets any inconvenience this may have caused.
Started 19 Nov 2013 20:30:00 by AAISP Staff
Closed 19 Nov 2013 23:22:00

19 Nov 2013 11:15:05
02 Oct 2013 09:07:54
Our monitoring has picked up evening latency on BT 21CN lines on the Bishopsgate exchange. This is happening between 8pm and 1am. We have opened an Incident with BT. This is not affecting TalkTalk Wholesale lines.
02 Oct 2013 09:51:39
BT will be monitoring and testing these affected lines this evening.
03 Oct 2013 10:34:07
This is still happening.
07 Oct 2013 15:24:31
BT have no updates, but are escalating this issue internally.
08 Oct 2013 12:52:33
BT investigated this last night and advised that they did not observe any excessive utilisation. So they liaising with BT Technical Services today.
09 Oct 2013 14:31:14
Update from BT: BT Technical Services have suggested to BT TSO Surveillance that a Switch of equipment would need to be facilitated and then further tests implemented after the switch has taken place.
11 Oct 2013 08:17:26
Latest update at 8.36am 10.10.2013 is that the equipment switch last night did not resolve your issue and that BT TSO have emailed BT Technical Services to again reinvestigate the Broadband latency problem.
11 Oct 2013 15:53:48
UPdate from BT: The latest update on this is that BT TSO whilst liaising with BT Technical Services have now involved BT Design to try and investigate this issue further. All three organisations are working together now to try and find a way forward to resolve this for you and your customers.
Resolution Issue resolved.
Started 02 Oct 2013 09:00:00
Closed 19 Nov 2013 11:15:05

21 Oct 2013 16:04:00
21 Oct 2013 15:57:52
TalkTalk Wholesale lines are currently off line. We are investigating.
21 Oct 2013 15:59:09
Some lines are coming back online..
21 Oct 2013 16:01:56
Other wholesalers are having similar problems
21 Oct 2013 16:04:56
Most lines are back online.
21 Oct 2013 16:20:42
We had notified TalkTalk at the start of this, they have replied saying that they have identified some network alarms. We'll update when we get more information. For now this fault is closed as lines are back online.
21 Oct 2013 16:30:43
TalkTalk confirmed that this affected many other of their wholesalers.
23 Oct 2013 12:01:23
We've not had the report from TT yet, but we have chased TT for it.
15 Nov 2013 16:50:54
This is the report from TalkTalk regarding this incident:
Problem Management have carried our further investigations. Please see the root cause below and preventative measures:
On Monday 21/10/2013, following some network device reboots, traffic was lost on two aggregate interconnects. We confirmed this using graphs on Cacti. Investigations were carried out by the B2B team and at 3:53pm on Monday 21st October a configuration addition was implemented on the ldn-vc1.thn device to try and load balance traffic over the two interconnects. Unfortunately this change affected the global routing of all traffic on the box (including management and customer data traffic). As part of the standard B2B procedure, the commit confirmed feature was used on the device when the change was made which resulted in the device returning back to normal service (management and data traffic) after 2 minutes. Following a review of this incident by B2B it was determined that the change was high risk. B2B processes have now been changed to always perform risk analysis on any future configuration changes. As well as this, any future configuration changes deemed necessary should be completed out of hours via the TTT PEW change process.
Sincere apologies for any inconvenience this has caused.
Resolution Summary of events:
Lines went off at 15:53
The started coming back online at 15:56
Most, if not all lines were back online by 16:04
We will have a report from TalkTalk as to the reason for this later today (22nd)
Started 21 Oct 2013 15:52:37
Closed 21 Oct 2013 16:04:00

09 Oct 2013 11:52:09
16 Aug 2013 15:35:36
We are currently moving a lot of BE lines over to TalkTalk Wholesale backhaul - customers are being emailed individually on this, however we do have more details at: http://aa.net.uk/broadband-2b.html

09 Oct 2013 11:51:49
29 Aug 2013 19:09:32
Migrations to TalkTalk wholesale lines have been going ahead this week, mostly for Be backhaul but some people with multiple BT lines chose to change to BT+TT. It is going well. Apart from the odd mis-jumpered line (inevitable, sorry), we have had a few lines where the modem is fixed at annex-A ADSL2+, and unlike the Be DSLAM, the TT ones do not fall back to annex-A. So if you have such equipment, including the likes of Vigor V.120 set to annex A mode, you may need to set Annex-M, or contact support to change our end to Annex-A, or using clueless to change profile to an ADSL1 profile which is Annex-A at 8M max. That will get you on-line at the very least. It is not something we expected, so we did not warn people in advance about this. We had done hundreds of BT 20CN service migrations a couple of months ago without seeing issues like this. Most of the remaining migrations are happening tomorrow with a small number next week. if you have problems, and can get on irc out of hours, some staff may be about to help. During the day we are available by phone as well, obviously. Some migrates take a matter of a few minutes. Some an hour. It all depends on how the OpenReach engineer does the re-jumpering. Any longer and that is probably a problem (like the Annex A/M issues above). The speed on Talk Talk is very similar, with around half of the customers getting better than they did on Be. Those that are a lot slower tend to have older modems, and we are happy to work with them to try alternatives. Overall we are pretty pleased with the process. The graphs and profile controls on the Talk Talk lines are working will and giving people a lot of direct control. If you need help, to talk to the support staff. I appreciate that this is often happen during the day. We don't really have a way to get it done "out of hours". What I would say is that if an outage during the day is a big issue, you really need to consider a multiple line solution like our Office::1 package. The sales staff will be happy to explain options. I'd like to thank everyone for their patience and understanding while we carry out this work. Any questions, do ask.

04 Oct 2013 09:00:00
04 Oct 2013 09:07:46
Lines are down on the Manor Park exchange. BT are aware of a fault affecting lines on the exchange, area code 01928.
Resolution BT fixed by 9am same day.
Started 04 Oct 2013 02:00:00
Closed 04 Oct 2013 09:00:00

04 Oct 2013 08:54:32
02 Oct 2013 14:48:48
We are seeing continuous packet loss (~10-20%) on TalkTalk Wholesale lines on the Kennford Exchange. This has been reported to TalkTalk and they have reported back that they see a possible network problem at their end.
03 Oct 2013 10:33:51
This is still happening.
03 Oct 2013 13:58:06
BT have updated us saying there are no further updates, but they have escalated it and they will send an update tomorrow.
Resolution Fault fixed. Problem was with line card. TalkTalk are still doing some diagnostics on these lines though.
Started 02 Oct 2013 14:46:27
Closed 04 Oct 2013 08:54:32

30 Sep 2013 10:25:21
03 Jan 2013 09:59:26

The 'per IP stats' usages pages are not working very well at the moment. Some customers are not seeing any usage, and some are seeing very little usage, and others are seeing correct amounts of usage!

This is being looked in to.

This does not affect the 'Line' usage or any billing based usage records. 

11 Apr 2013 12:25:10

We are sorry for how long this has been ongoing.
We are still trying to resolve the issue, however it is taking a lot longer than we expected.

We do not currently have an ETA however we will update this status once we have further news.

02 Aug 2013 09:13:39
The IP Stats are now back online. We'd be interested to hear from customers where the per IP stats are reporting very different usage when compared to the usage in the hourly usage tables. Remember that the IP Stats are a rough guide, they are not used for billing, but are useful to see usage on an per IP basis for diagnostics etc.
07 Aug 2013 10:53:32
At the moment, Per IP Stats are only being recorded for customers on half of our LNSs - Customers on A and C Gormless should see stats, but B and D will not. The CQM graph will show which Gormless you are on.
30 Sep 2013 10:26:39
We will close this post for the moment and the job is with our Engineering team. At the moment per IP stats is working on some but not all lines. Rather than withdraw the feature, we'll keep it as it is and this will be further investigated.
Started 03 Jan 2013 09:56:05
Closed 30 Sep 2013 10:25:21

30 Sep 2013 09:58:46
30 Sep 2013 09:19:25
Good news for existing and new Home::1 Customers. From 1st October 2013, the inclusive usage allowance on Home::1 will go from 50GB per month up to 100GB per month.

Higher usage levels change too. The levels will be 100GB, 200GB, 300GB for same prices as previously 50GB, 150GB, and 250GB

Customers do not need to do anything to take advangage of this usage upgrade.

More info on http://aa.net.uk/broadband-home1.html

Started 30 Sep 2013 09:00:00

0013-10-02 10:00:00
17 Sep 2013 16:12:40
We have been notified of the below planned maintenance window affecting some BE DSL connections: Date - 29/09/2013 Time Start - 11:00PM Time Finish - 11:00AM Duration: Up to 12 hours Exchanges affected: Brookwood Godalming Haslemere Marlow Evington Catford Brixton Grove Park
Started 29 Sep 2013 23:00:00 by BE
Closed 0013-10-02 10:00:00
Previously expected 30 Sep 2013 11:00:00 (Last Estimated Resolution Time from BE)

14 Sep 2013 08:19:18
11 Sep 2013 08:52:22
We are doing some router upgrades at the weekend - this is part of an ongoing program to imrpove the connectivity within our network to provide a better service to customers. We have already upgraded some of our transit connectivity. Last time we did upgrades there was some brief disruption to traffic for 2 to 3 seconds, which was enough to cause some issues with one of our wholesale customers. Part of this upgrade is specifically to try and impove this in the future, but at this stage we are expecting a similar level of disruption during the process. If all goes to plan it will mean future upgrades should be a lot more seamless. We are also doing rolling LNS change overs and upgrades over night during the next few days.
15 Sep 2013 14:17:01
We are doing some further work today (Sunday) but expect no disruption.
Resolution All went well
Started 14 Sep 2013
Closed 14 Sep 2013 08:19:18
Previously expected 16 Sep 2013

14 Aug 2013 10:00:00
13 Aug 2013 21:26:59
We are investigating...
13 Aug 2013 21:41:56
about 50% or so of our BE lines are seeing a mix of low level packet loss, higher latency and latency spikes. Some lines are also seeing very frequent disconnects. We have informed BE.
13 Aug 2013 21:50:35
BE have reported problems regarding 7 exchanges which may be related to this. They say: "We are currently experiencing an unplanned outage at our Crownhill (WWCRWN), Devonport (WWDPRT), Plympton (WWPTON), Saltash (WWSALT), St Budeaux (WWSBUD), Plymouth (WWPYTH) and Plymstock (WWPSTK) exchanges. Our engineers are informed and investigating. Apologies for the inconvenience caused."
13 Aug 2013 22:14:17
Lines have been back to normal since about 10:05pm.
13 Aug 2013 22:16:38
We suspect BE may have been re-routing traffic in their network as a result of the exchange problems which meant many other lines were being routed over congested links. We've not had this confirmed yet though.
13 Aug 2013 22:17:29
(This was also affecting non-AA BE lines.)
13 Aug 2013 22:59:05
We have a very small number of lines that have an increase in their minimum latency, the latency had jumped up by about 10-20ms. We have passed these lines on to BE for their comment.
13 Aug 2013 23:00:12
An update from BE regarding their problems with the exchanges: "Crownhill (WWCRWN), Devonport (WWDPRT), Plympton (WWPTON), Saltash (WWSALT), St Budeaux (WWSBUD), Plymouth (WWPYTH) and Plymstock (WWPSTK): The links are back restoring all connectivity. Engineers are still investigating for the cause so future failures can be prevented. "
14 Aug 2013 21:15:07
We've had an update from BE as they have been investigating this, here is the information "I have spoken to O2 throughout the day about this case and it is believed that the cause may have been due to the exchange outages in the south-west areas, as you suspected. The case has been elevated to O2's Network team who have since passed it to their Transport Services team that will be responsible for investigating the exact cause of the issue and also reaffirming that the problem has been resolved."
Resolution BE did have an outage affecting a number of exchanges (listed above) in the south of England. We suspect this also caused re-routing of traffic within their network which caused latency and loss on other lines.
Started 13 Aug 2013 21:15:26
Closed 14 Aug 2013 10:00:00