Ai Networks Ltd
All Systems Operational
London Network   Operational
National MPLS Network   Operational
Northern Europe Network   Operational
Voice Platform   Operational
US Network   Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Scheduled Maintenance
Core Network Maintenance Feb 21, 22:00 - Feb 22, 02:00 GMT
We will be undertaking scheduled maintenance to cabling infrastructure in our Stevenage site. The work is not expected to interrupt services, but we will be manipulating cabling and power infrastructure and at times, we will be decreasing the level of resilience. Therefore, for the duration of the window, services should be considered at-risk in the Stevenage site, and for Welwyn Garden City whose main backup route is via Stevenage.
Posted on Jan 31, 11:19 GMT
We will be undergoing scheduled maintenance affecting the London core exchange network. This involves breaking the ring of exchanges in central London to connect a new site in the London BT tower.

During the work, we will make use of backup routes to ensure that interruptions to live traffic are limited to short periods of network convergence. However, for the duration of the window, the network should be considered at risk.

The work will also affect traffic at the points of ingress to the exchange ring which include London Interxion and London Volta. These sites should also be considered at risk.
Posted on Feb 5, 11:14 GMT
Past Incidents
Feb 17, 2019

No incidents reported today.

Feb 16, 2019

No incidents reported.

Feb 15, 2019

No incidents reported.

Feb 14, 2019

No incidents reported.

Feb 13, 2019

No incidents reported.

Feb 12, 2019

No incidents reported.

Feb 11, 2019

No incidents reported.

Feb 10, 2019

No incidents reported.

Feb 9, 2019

No incidents reported.

Feb 8, 2019

No incidents reported.

Feb 7, 2019

No incidents reported.

Feb 6, 2019

No incidents reported.

Feb 5, 2019
Resolved - The network is confirmed as fully operational. We will be following up with an incident report as soon as possible.
Feb 5, 13:00 GMT
Monitoring - Most services appear to be restored, however we are continuing to monitor closely for any remaining issues.
Feb 5, 12:11 GMT
Update - A fibre link between Telehouse North and Stevenage appears to have experienced an issue. Our engineering team is investigating further.
Feb 5, 12:06 GMT
Update - We are continuing to investigate this issue.
Feb 5, 12:01 GMT
Investigating - We are investigating alerts for network connectivity.
Feb 5, 12:00 GMT
Resolved - We are setting this as resolved as the symptoms have been clear for some time.
Feb 5, 11:17 GMT
Monitoring - A fix has been implemented and we are monitoring the results.
Feb 1, 11:48 GMT
Update - We have chased Amazon further today for a response. We are also investigating a workaround involving forcing the affected traffic via an alternative route.
Jan 31, 14:47 GMT
Update - We are continuing to chase 3rd-party networks for resolution to this issue. Symptoms appear to appear daily at 16:00 approximately, and continue for around one hour.
Jan 31, 10:57 GMT
Update - We are continuing to investigate this issue.
Jan 30, 18:44 GMT
Update - We are aware that the issue recurred around 1600 GMT. We are engaging conversations between our tier-1 peer and Amazon to ensure this is resolved ASAP.
Jan 30, 16:42 GMT
Update - Our investigations are continuing, however the symptoms have now subsided. We will provide a further update today.
Jan 30, 09:56 GMT
Update - Under our request, the peers are discussing the issue. We are expecting an update within 24 hours.
Jan 29, 16:55 GMT
Investigating - We are investigating some packet loss in the connection between one of our tier-1 peers and the Amazon region in Seattle. The case has been reported to both Amazon and the peer, and investigations are ongoing.
Jan 29, 16:44 GMT
Resolved - This appears to be resolved, however we are continuing to monitor the issue which was affecting a very small percentage of calls.
Feb 5, 10:33 GMT
Investigating - We are investigating reports of a small number of customers experiencing voice issues.
Feb 5, 10:11 GMT
Feb 4, 2019

No incidents reported.

Feb 3, 2019

No incidents reported.