Our Network:
Major Outages


Minor Outages


Happening Now


Future Planned


Suppliers' Network:
Recently Closed Events:
Sep 27, 03:46 PM (1 day ago)
Sep 27, 10:00 PM (17¾ hours ago)
Sep 28, 08:00 AM (7¾ hours ago)
42466 / AA42466
    Post created: 1 day ago by Andrew

    Following on from the problems this morning, TalkTalk are performing some emergency work overnight, tonight. The work will start at 10PM and will carry on through to 6AM. They say that their work before midnight should not impact circuits, but the work after midnight may cause some reconnects.

    13 hours ago by Andrew

    as of 02:15, TalkTalk's work is underway - they have taken down our link to them in Telehouse. This did cause lines to drop and reconnect. There may be further reconnects when they bring the port back up.

    8½ hours ago by Andrew

    TalkTalk's planned work has failed and has turned in to an outage. Our port to them in Telehouse is still down. However, our customers are unaffected by this as our link to TalkTalk in our Equinix datacentre is working. We'll update this post as we receive updates from TalkTalk.

    7¾ hours ago by Andrew

    TalkTalk have just bought our Telehouse port back in to service - this has caused some lines to drop and reconnect.

    7½ hours ago by Andrew

    Lines are still re-connecting... Those still down should be back up very soon.

    7½ hours ago by Andrew

    TalkTalk seem to be forcing all lines to PPP reconnect, some lines are taking a few minutes to log back in. Lines not back online now should be on soon though.

    7¼ hours ago by Andrew

    TalkTalk lines still seem to be very happy. We've shut down our link to TalkTalk in Telehouse to force all lines through our other link.

    7 hours ago by Andrew

    Lines are looking stable now. Our Telehouse link is still down, we'll leave it that way until we get an all-clear from TalkTalk.

    5¼ hours ago by Andrew

    TalkTalk say they have restored the Telehouse service at their side. We will keep that link down for the moment as they may well schedule more work on it. Our TalkTalk services have been stable since 08:30.

    5¼ hours ago by Andrew

    TalkTalk say they have restored the Telehouse service at their side. We will keep that link down for the moment as they may well schedule more work on it. Our TalkTalk services have been stable since 08:30.

    7¾ hours ago by Andrew

    TalkTalk have emergency overnight work that failed and turned in to an outage causing circuits to drop. We took our Telehouse connection out of service and lines reconnected via our Equinix link and have been stable since 08:30. We'll leave the Telehouse link down for the moment in case TalkTalk schedule further work on it.

  • Closed
Broadband blip graph

The graph shows the last few hours of logins and logouts of ADSL, VDSL, SIMs and L2TP circuits.

The current time is on the left. Green is login, red is logout.

If there are spikes, then this shows a large number of logouts, which may indicate an outage or planned work happening.

You can click on a spike to search for incidents or maintenance that were open around that time.

About our status page

This is the status page of Andrews & Arnold Ltd.

Our status page shows outages (problems) and maintenance (planned work) that happen on our own network and systems and also that of our suppliers networks and systems. We try and ensure this site is updated as soon as possible with incidents as they happen. Live discussion of issues is usually available on IRC.

The last update was Today 10:34:33

Contacting us
Our support number is 033 33 400 999, or you can email support@aa.net.uk or text 01344 400 999 to raise a support ticket.

Spotted a Major Service Outage? (MSO)
A Major Service Outage disrupts the service of multiple customers simultaneously. If you believe that a problem affects multiple customers, and is not mentioned here already, text the number above. Begin the text with "MSO". This alerts multiple staff immediately, waking them if necessary. False alarms (i.e. raising MSO for a single line being down) may result in your number being prevented from raising MSO alerts in future. More info.

Regular Maintenance
Thursday evenings, from 10pm, are designated as a general maintenance window where we will perform non-service affecting updates.

Congestion Reports

Every night we analyse the packet loss and latency from us to our carriers and also from us to each of our customers.

A&A to Backhaul Carriers

This table show un-errored seconds on our connections in to our carriers for the past 7 days. Our aim is for all of these to be at 100%.

Links to carriers

We have links to back-haul carriers BT and TT.

Our target is that we operate a uncongested links to the carriers. This means that if the general trend is that the link will be getting full we order more capacity from carriers. The capacity we order is expensive, takes time to change and has minimum terms. This means it can be difficult to perfectly manage the traffic. We allow some head room but not more than necessary. It is technically impossible to guarantee that the link is always uncongested (not without having a pipe the size of all internet links in the world added together) but by careful monitoring and allowing enough headroom we can aim for that target.

This table shows an analysis of how well we meet our target.

Unerrored seconds

The unerrored seconds report is the simplest statistic to understand. If we drop even a single packet in a second then this counts as an errored second. Given that we can be handling hundreds of thousands of packets every second, this can be a very sensitive measure of congestion. Bear in mind we will drop the larger packets first which will normally be TCP which re-sends the dropped plackets. This helps ensure VoIP and interactive uses of the internet are unaffected.

Daytime unerrored seconds are based only on 9am to 6pm Monday to Friday


We also consider 100 second samples. If we have reduced the throughput of non-premium lines at all (as a result of dropped packets for several seconds in a row) then the whole 100 seconds is considered to have affected non-premium customers. Because we are looking at 100 seconds at a time it is possible for very short busts of traffic to cause this to show a worse figure than the unerrored seconds. Even if traffic was reduced by 0.5% for part of the 100 second period the whole 100 seconds counts as errored.


Considering the 100 seconds samples, there is a limit to how much we will reduce the non-premium customers. If that limit is reached then we consider the whole 100 second sample is having an impact on premium lines. This is a sign of much more severe bursts of congestion for several minutes. Bear in mind, a single 100 second sample in a day is more than 0.1% of the day, and even if this does happen VoIP and interactive services should be unaffected.

Read more.
Updated 1 year ago. Link congestion stats
Link Week days 9-6 24 hour Non-premium Premium
Backhaul Carrier to Customers

This report can pinpoint congestion in exchanges, BRAS's or particular areas of the country.

Method of analysis

Every line is sent an LCP echo every second and loss and latency measured. This is summarised per 100 second sample and archived for every line for each whole day. The previous day is then analysed each morning and the above table is updated.

Each line is considered to pass, fail or be inconclusive. Inconclusive includes lines where samples have too much upload or download which could themselves cause higher loss or latency to be observed. Lines with less than 18 hours on-line are excluded totally.

Latency is considered against a reference base-line latency for the circuit, and this has to be present for several hours to be considered. As such, lines without clean latency monitoring (some makes of router) are excluded.

For an area to show in the above table there must be no lines that pass at all, and at least 50% of the lines must fail (the rest being inconclusive). Where we have very few lines we require 80% to fail (and none to pass) to show on this list. The area must also have enough lines, so some smaller exchanges will not be detected.

The size stated is what percentage of our total lines are in the affected area.

The block graph under each report for yesterday is based on an average of valid samples for each line for each hour, and then taking the lowest value of all lines in the affected area, so the loss and latency shown is something that is affecting every line in an area.

Updated 1 year ago.

There are no currently identified congestion spots

We are not able to automatically identify all congestion spots so this does not mean there are not problem areas, do contact Support if you think you are suffering from congestion.