17
Nov
2017
12:19

We apologise to our customers with BT lines who have been affected by the outage this afternoon. Our wholesale supplier for BT connected lines is investigating the cause of the issue.

Apologies to those customers affected.

Posted by Yolanda Zyczynska

29
Aug
2017
08:44

We are observing packet loss affecting cartain data paths in our AMS datacentre, which is being investigated.

Posted by Kevin Hones

11
Aug
2017
09:13

Customers who have a TalkTalk connected service may have experienced a glitch in service for a minute or so at around 09:00 this morning, normal service is now running.

The cause of the glitch is unknown at this time, as soon as we have more information from TalkTalk we will post an update.

We apologise for any inconvenience caused.

Posted by Yolanda Zyczynska

20
Jul
2017
13:03

We apologise to our customers with BT lines who have been affected by the outage this afternoon. Our wholesale supplier for BT connected lines carried out investigative testing following the issues last week and unfortunately made an error with the configuration on one of their switches. The configuration change has been rolled back and the service to customers restored.

Apologies to those customers affected.

Posted by Yolanda Zyczynska

14
Jul
2017
10:43

Update 12:17 – All lines have now reconnected and been stable for approximately one hour.

Our wholesale supplier for BT connected lines is experiencing severe problems this morning. Once they have rectified the situation we expect affected lines to reconnect automatically. We will monitor to ensure this is so.

Apologies to those customers affected.

Posted by Yolanda Zyczynska

13
Jul
2017
20:47

Update 21:50 – All lines have now reconnected and been stable for approximately one hour.

Our wholesale supplier for BT connected lines is experiencing severe problems this evening. Once they have rectified the situation we expect affected lines to reconnect automatically. We will monitor to ensure this is so.

Apologies to those customers affected.

Posted by Kevin Hones

26
May
2017
16:04

We are experiencing interruptions to our connectivity with one of our upstream providers, Pulsant, this afternoon.

As we use diverse suppliers for transit we switched the Pulsant transit off until they had fixed their issue.

We apologise for any inconvenience caused.

Posted by Yolanda Zyczynska

04
May
2017
14:25

Update: Pulsant have notified us that they will be performing emergency maintenance between 21:00 and 23:00 this evening related to the earlier outage.

This maintenance should be considered as an ‘at risk’ time, rather than a definite outage.

Earlier message:

We unfortunately experienced network outages outwith our network earlier today.

Our infrastructure was working normally but the issues were with one transit provider.

The issue was with Pulsant; more information can be found at http://status.pulsant.com/

We apologise for the three blips these issues caused.

Posted by Paul Malkowski

10
Apr
2017
16:25

We would like to offer our apologies for the brief network outage that happened in the last hour.

We were monitoring traffic using debug on one of the main switches and unfortunately ran out of memory.

As soon as we realised what was happening we reversed the debug monitoring and normal service was resumed.

Posted by Paul Malkowski

05
Apr
2017
14:20

We experienced a blip with Pulsant transit coming out of Pulsant 1 & 2 in Maidenhead early this afternoon.

As we use diverse suppliers for transit we switched the Pulsant transit off until they had fixed their issue.

They currently have a workaround in place and everything seems to be normal again.

We have switched our Pulsant transit back on.

Posted by Paul Malkowski

02
Mar
2017
13:27

We would like to apologise for not informing everyone of the maintenance window between 5pm and 7pm on Tuesday 28 February 2017.

We were moving a physical between racks which hosted some of our servers including knockando our mail server.

Posted by Paul Malkowski

09
Dec
2016
20:08

We would like to apologise for the outage affecting various services between approximately 18:15 and 18:45 this evening.

This was caused by a configuration error whilst deploying a private interconnection with a specific customer. Unfortunately a layer2 routing loop was created, which flooded a core network ethernet segment with broadcast traffic.

Posted by Kevin Hones

Current Status

Status Archive