Last 10 posts, sorted by last updated
Limit to posts

MAINTENANCE Assumed Completed TalkTalk
AFFECTING
TalkTalk
STARTED
Dec 02, 01:00 AM (6 days ago)
DESCRIPTION
TalkTalk are performing various upgrades overnight which are causing PPP drops on a large number of lines.

MAINTENANCE Assumed Completed General
AFFECTING
General
STARTED
Oct 05, 03:00 AM (2 months ago)
DESCRIPTION
We will be performing software upgrades on various FireBrick routers and LNSs across our network, starting this week. These are scheduled to happen between 1AM and 4AM and will happen over the course of a few weeks. The process of upgrading our LNSs will involve a line drop and reconnect of broadband lines.

MAINTENANCE Assumed Completed SIP2SIM
AFFECTING
SIP2SIM
STARTED
Sep 10, 10:07 AM (2¾ months ago)
DESCRIPTION

This affects SIP2SIM customers who would previously have seen short CLI on calls to their SIM - eg where an incoming call to the SIM would have shown the short extension number of a caller on the same PABX.

Our SIP2SIM service is intended to allow a SIM in any phone or any 'dumb' phone to work as a SIP extension, either a SIP number provided by A&A or an extension on a customer's own SIP PBX. This meant that, for example, for an internal call, you would see the call from that internal extension number. This was not perfect, e.g. a call from extn 401 might show as +401, but it worked.

A change in Ofcom policy has meant that we now have to send a 'valid' looking CLI SIM. This is fine for normal calls from 'outside' your PABX as they will have the proper CLI of the caller, but customers running their own PBX may well be using short extension numbers, and 'internal' calls on the customer PBX between extensions would be sending the extension number as the CLI. eg a three digit extension number such as 402 or 403 etc.

In situations where an invalid CLI is used - eg an 'internal' call to the SIP2SIM extension, we have to now change the CLI to look like a 'valid' CLI.

Our workaround is to change the CLI to be: +11, then a number of zeros, then the original CLI requested, so +11 and 9 further digits.

eg, if you have two 'internal' extension numbers, 402 and 403. 402 is a normal SIP phone, and 403 is registered from a SIP2SIM. A call from 402 to 403 will have the CLI changed to: +11110000402

This does mean a call back to such a number would hit your PABX with this otherwise invalid number. We suggest you make your PABX map these to internal extensions if possible.

This does somewhat break the philosophy of our SIP2SIM service as a SIM being a normal SIP extension. We are not happy about this. This change is mandated by Ofcom and we have no choice.


MAINTENANCE Completed Email
AFFECTING
Email
STARTED
Nov 29, 10:00 PM (8 days ago)
CLOSED
Nov 30, 12:03 AM (8 days ago)
DESCRIPTION
Further to the work last Friday (https://aastatus.net/42417) we will be doing some more work on our database cluster. This will happen tonight from 10PM (Monday 29th November.) During this time webmail will be offline and there may be delays to incoming email.
Resolution: This has been completed.

MINOR Closed email
AFFECTED
email
STARTED
Nov 26, 10:07 AM (11½ days ago)
CLOSED
Nov 26, 11:33 PM (11 days ago)
DESCRIPTION
Similar to yesterday's problem, we're investigating a problem that is affecting access to webmail and also delays with incoming email.
Resolution:

MAINTENANCE Completed Email
AFFECTING
Email
STARTED
Nov 26, 10:00 PM (11 days ago)
CLOSED
Nov 26, 11:31 PM (11 days ago)
DESCRIPTION
In light of the recent problems with our database cluster we have scheduled at short notice a maintenance period to investigate the problem further. This will happen tonight from 10PM (Friday 26th November.) During this time webmail will be offline and there may be delays to incoming email.
Resolution: This work has been completed. We believed there was inconsistencies in the database which caused problems with the cluster - we have re-created the cluster and will monitor and investigate further if problems continue to occur. We do apologise for the intermittent disruption this has had to customers over the past two days.

MINOR Closed Email
AFFECTED
Email
STARTED
Nov 25, 12:10 PM (12½ days ago)
CLOSED
Nov 25, 02:29 PM (12½ days ago)
DESCRIPTION
We're investigating a problem that is affecting access to webmail and also delays with incoming email.
Resolution:

MAJOR Closed access
AFFECTED
access
STARTED
Nov 25, 02:43 AM (12¾ days ago)
CLOSED
Nov 25, 02:48 AM (12¾ days ago)
DESCRIPTION
We're investigating a routing problem at the moment.
Resolution:

MAINTENANCE Completed Network
AFFECTING
Network
STARTED
Nov 25, 02:00 AM (13 days ago)
CLOSED
Nov 25, 03:08 AM (12¾ days ago)
DESCRIPTION
We are planning a couple of jobs for 2AM on Thursday 25th November that should have no impact to customers but should be considered a period of 'at risk'.
The first job involves reconfiguring the connectivity between two of our racks in London, the second job is regrding the IP routing between Maidenhead and London.
Resolution: This work has been completed. There was a short routing issue caused by the Maidenhead work and that will be investigated further at a later date.

MAINTENANCE Completed Control Pages
AFFECTING
Control Pages
STARTED
Nov 21, 10:00 AM (16½ days ago)
CLOSED
Nov 21, 12:00 PM (16½ days ago)
DESCRIPTION
We will be carrying out maintenance work on our control pages ages on Sunday the 21st of November. The control pages will be unavailable for a period of time during this work, but we'll aim to make any disruption as brief as possible.
Resolution: This was completed