• DDCL / City Reach - London, UK Operational
  • Iron Mountain AMS1 - Amsterdam, NL Operational
  • Equinix LD8 - London, UK Operational
  • Telehouse North Two - London, UK Operational
  • Interxion PAR-5 - Paris, FR Operational
  • Interxion ZUR-1 - Zurich, CH Operational
  • Interxion FRA-15 - Frankfurt, DE Operational
Fibre Outage [RESOLVED]

July 19, 2021, 11:47 AM - Europe/London

We are experiencing a fibre outage between Equinix LD8, London and Iron Mountain AMS1, Amsterdam. Traffic was automatically re-routed due to our redundant dark fibre network and no downtime should have occurred.

You will see an increased latency during this time from London to Amsterdam as traffic is now routing through Paris.

This status alert is primarily to notify users that there is now an active at-risk period until the fibre span has been fully repaired and brought back online.

Please contact us via support tickets if you have any further questions.

3 updates posted.

Emergency reboot of FPC's in City Reach, London [RESOLVED]

July 1, 2021, 4:11 PM - Europe/London

We will be rebooting a few MPC's in City Reach, London as they are producing errors, high latency and packet loss. Unfortunately we have exhausted all methods to fix this without having to reboot.

During the reboots it may cause higher packet loss and latency for 5-10 minutes.

We apologize for the inconvenience this may cause.

9 updates posted.

Dark Fibre Cut [RESOLVED]

March 24, 2021, 1:57 PM - Europe/London

We are experiencing a dark fibre cut between City Reach, London and Equinix LD8, London. Traffic was automatically re-routed due to our redundant dark fibre network and no downtime should have occurred.

This status alert is primarily to notify users that there is now an active at-risk period until the dark fibre span has been fully repaired and brought back online.

Please contact us via support tickets if you have any further questions.

2 updates posted.

Network disruption 05.02.2021 - AS 25396 [RESOLVED]

February 5, 2021, 10:31 PM - Europe/London

Hello,

We're currently investigating a fault with the rdp process on a couple of our Juniper routers that had failed at approximately 22:00 GMT this evening.

The cause of this is currently unknown but this did cause a cascade of problems to neighbouring routers with high volumes of BGP updates being sent out.

We're currently reviewing the log files from these routers and will provide more information as soon as possible.

Apologies for any inconvenience caused, and thank you for your patience.

- HydraCom NOC

1 updates posted.

Interxion PAR5 Core Offline [RESOLVED]

February 3, 2021, 2:32 PM - Europe/London

We are investigating an issue with Interxion PAR5. At current the router is not responsive. We will update here with further information once we have it.

10 updates posted.

High Latency / Packet Loss [RESOLVED]

November 22, 2020, 5:41 PM - Europe/London

Our Equinix LD8 core is having a line card replaced due to a fault.

An increased latency may affect servers while this is happening.

2 updates posted.

Iron Mountain AMS1 - Line Card Failure on Core Router - At Risk [RESOLVED]

November 17, 2020, 5:34 PM - Europe/London

A recently installed 100G line card has failed in our core MX960 router in Iron Mountain AMS1. Traffic has automatically failed over to the other cards within the router and traffic should not be affected.

As we have secondary links for all T1's and waves to our other sites, this is just an at-risk notification.

3 updates posted.

Equinix LD8 Core Offline - At Risk [RESOLVED]

August 18, 2020, 4:46 AM - Europe/London

Our Equinix LD8 core is currently offline after the site was evacuated due to a fire alarm. We expect this to be a site-wide power related issue.

All traffic was automatically rerouted to Telehouse North Two and so this single site outage is not service affecting.

9 updates posted.

AMS-IX Port Hard Down [RESOLVED]

April 1, 2020, 12:42 PM - Europe/London

Our AMS-IX ports are currently hard down in Iron Mountain AMS-1. All traffic was automatically re-routed to other exchanges and T1's.

No services are disrupted, this status notification is informational only.

3 updates posted.

Covid-19

March 23, 2020, 8:49 PM - Europe/London

Over the last few weeks we’ve been following the emerging Corona Virus outbreak in the news and preparing the company in the event of it escalating further. With the outbreak appearing to spread further we expect these internal preparations to go into effect over the next few weeks.

What does this mean for you as a customer?

To begin with, we expect no immediate changes to setup times, ticket response times or stock procurement. We’ve taken measures internally to guarantee that we have enough general stock for the next few weeks to fulfill any new orders and deal with any emergencies that do arise.

As things progress, we do expect our setup times for new orders and part changes to increase as we try to limit our staff’s exposure to other members of the public, as well any custom builds (ones not listed on our website) to be delayed indefinitely.

During this time we will still have systems in place to deal with emergency callouts and will still have staff active via our ticket system.

As things progress we will make sure to update you and provide you with additional information. Any major changes will be announced via twitter and will be posted on our status page. If you have any questions at all then please open a ticket with our team, we’ll be happy to help.

3 updates posted.

Switch Offline - sw0-r6.8 [RESOLVED]

February 15, 2020, 1:56 PM - Europe/London

sw0-r6.8 has gone offline roughly 25 minutes ago in our Amsterdam data centre, this will be affecting 24 blades with the following ID's:

AMS-6-8-6-U1-1 to 12
AMS-6-8-6-U2-1 to 12

We have dispatched engineers to resolve the issue.

3 updates posted.

AMS <-> LON Connectivity at risk [RESOLVED]

January 6, 2020, 9:57 AM - Europe/London

Connectivity between servers in Amsterdam and London is at risk this morning from 5:00 GMT onwards because of a subsea fibre cut with one of our fibre providers GTT/Interoute. Our secondary set of waves from provider Zayo are still operational and have ample capacity.

Due to subsea fibre cuts taking days to repair, if there is any unplanned maintenance windows with our secondary Zayo fibre we will have to alter routing policies to try and avoid any issues as much as possible.

If you have any questions please don't hesitate to contact us.

2 updates posted.

AMS <-> LON Connectivity at risk [RESOLVED]

October 3, 2019, 7:50 PM - Europe/London

Good evening everyone,

Connectivity between servers in Amsterdam and London is at risk this evening from 22:00 BST on wards because of an overlap in maintenance by our fibre providers Zayo and GTT/Interoute for our primary and secondary circuits from our London metro network to Amsterdam.

Our primary circuits from Zayo went down for maintenance on the 30th of September and were scheduled to be back up earlier today, however due to storm conditions and high tides the maintenance crew have not been able to complete the splicing work on the subsea fibre cable.

Our backup circuits from GTT/Interoute are scheduled to be taken offline for up to 7 hours from 22:00 GMT to complete joining works a mile away from the data centre where the fibre terminates at in Amsterdam.

We're going to be altering routing policies to try and avoid any issues as much as possible, but there could potentially still be some impact until the GTT/Interoute circuits are back online (this maintenance window closes at 05:00 GMT).

If you have any questions please don't hesitate to contact us.

1 updates posted.

Dark Fibre Cut [RESOLVED]

May 5, 2019, 4:49 PM - Europe/London

We are experiencing a dark fibre cut between City Reach, London and Equinix LD8, London. Traffic was automatically re-routed due to our redundant dark fibre network and no downtime should have occurred.

This status alert is primarily to notify users that there is now an active at-risk period until the dark fibre leg has been fully repaired and brought back online.

Please contact us via support tickets if you have any further questions.

2 updates posted.