All Services Fully Operational

Global IP Transit




Fully Operational

MPLS/VPLS/L2VPN




Fully Operational

Colocation




Fully Operational

DWDM/Wavelength




Fully Operational

Website / Domain Hosting




Fully Operational

Support Desk Operations




Fully Operational

Public Cloud




Fully Operational

Scheduled Maintenance

[CDC-ID: #252838] UPS Maintenance NotificationPlanned Maintenance

Schedule

June 16, 2025 09:00 - 18:00 BST

Components

Colocation

Locations

ME14

Description

Engineers from Riello will be performing a UPS service across a number of our systems that supply our Maidstone facility. Each feed will be worked on separately, and each UPS will be switched to bypass only after the load has been transferred to our generator farms. Although minimal, customers should consider one of their power feeds to be ‘at-risk’ during the period detailed above. Customers with diverse power supplies will only have one feed at risk at any given time, diverse feeds at our facility come from different ATS+UPS chains and are totally independent. This is an at-risk notification only, we do not expect any customer impact during these works.
[CDC-ID: #252886] Network platform migration - Service ImpactPlanned Maintenance

Schedule

July 19, 2025 08:00 - 20:00 BST

Components

Global IP Transit, MPLS/VPLS/L2VPN

Locations

ME14

Description

CustodianDC are scheduling in works to migrate all Maidstone DF1 and DF3 customers from our older edge platform to our newer edge platform. This not only brings customers on to newer hardware, but it also brings them away from ageing patch panel infrastructure. It is important in this instance to note that customers may experience interface flaps while works are being performed even if they are not being moved in that moment. This is due to the level of intrusive works required to move customer connections. As a result please consider services to be at risk within these windows. It is also important to note that customers being moved over to this platform will no longer be part of our own STP instance and so customers will need to handle loop protection on their own infrastructure. Loops spotted on our network will have one port shut down to resolve the immediate loop potential and then those customers will be notified of the action at the end of the maintenance window. Customers that have BGP instances with us which are already on our core platform but receive L2 through our older edge will have one instance shut and moved to cleanly migrate them away and reduce impact. Customers that have BGP instances with us which are on our edge platform will have all sessions admin shut and then moved and re-established. Standard Flat and static route IPT services will but shut down unconfigured and then reconfigured on to the new platform. Backhaul services, protected or un-protected will be moved one at a time but will be affected in this window. In all cases our team will ensure that services look to have returned after migration before moving on to the next service. We will be moving customers one at a time within the window unless we have pre-agreed a time slot with you. For customers with a single feed we anticipate affected services will not have connectivity for 15 minutes and no more than 30 minutes unless we are required to roll back the service or perform troubleshooting. For customers with dual feed we anticipate affected services will not have connectivity for up to 30 minutes unless we are required to roll back the service or perform troubleshooting. Affected customers will require their cables to be shortened within our own infrastructure and so this will be done within the move, due to this you may see more than one interface flap as we will endeavour to bring services back up before disconnecting a single link one at a time to perform those L1 alterations. There are a large number of customer ports to migrate to the new platform so customers not affected in the first window should anticipate being affected in the second as we run sequentially though our infrastructure. For any remaining customers we will schedule a third window now, however anticipate that we will be able to cancel it at the end of the second window. For any questions or concerns regarding this maintenance please contact the NOC. This maintenance has been logged under [CDC-ID: #252886]
[CDC-ID: #252886] Network platform migration - Service ImpactPlanned Maintenance

Schedule

July 20, 2025 08:00 - 20:00 BST

Components

Global IP Transit, MPLS/VPLS/L2VPN

Locations

ME14

Description

CustodianDC are scheduling in works to migrate all Maidstone DF1 and DF3 customers from our older edge platform to our newer edge platform. This not only brings customers on to newer hardware, but it also brings them away from ageing patch panel infrastructure. It is important in this instance to note that customers may experience interface flaps while works are being performed even if they are not being moved in that moment. This is due to the level of intrusive works required to move customer connections. As a result please consider services to be at risk within these windows. It is also important to note that customers being moved over to this platform will no longer be part of our own STP instance and so customers will need to handle loop protection on their own infrastructure. Loops spotted on our network will have one port shut down to resolve the immediate loop potential and then those customers will be notified of the action at the end of the maintenance window. Customers that have BGP instances with us which are already on our core platform but receive L2 through our older edge will have one instance shut and moved to cleanly migrate them away and reduce impact. Customers that have BGP instances with us which are on our edge platform will have all sessions admin shut and then moved and re-established. Standard Flat and static route IPT services will but shut down unconfigured and then reconfigured on to the new platform. Backhaul services, protected or un-protected will be moved one at a time but will be affected in this window. In all cases our team will ensure that services look to have returned after migration before moving on to the next service. We will be moving customers one at a time within the window unless we have pre-agreed a time slot with you. For customers with a single feed we anticipate affected services will not have connectivity for 15 minutes and no more than 30 minutes unless we are required to roll back the service or perform troubleshooting. For customers with dual feed we anticipate affected services will not have connectivity for up to 30 minutes unless we are required to roll back the service or perform troubleshooting. Affected customers will require their cables to be shortened within our own infrastructure and so this will be done within the move, due to this you may see more than one interface flap as we will endeavour to bring services back up before disconnecting a single link one at a time to perform those L1 alterations. There are a large number of customer ports to migrate to the new platform so customers not affected in the first window should anticipate being affected in the second as we run sequentially though our infrastructure. For any remaining customers we will schedule a third window now, however anticipate that we will be able to cancel it at the end of the second window. For any questions or concerns regarding this maintenance please contact the NOC. This maintenance has been logged under [CDC-ID: #252886]
[CDC-ID: #252886] Network platform migration - Service ImpactPlanned Maintenance

Schedule

July 26, 2025 08:00 - 20:00 BST

Components

Global IP Transit, MPLS/VPLS/L2VPN

Locations

ME14

Description

CustodianDC are scheduling in works to migrate all Maidstone DF1 and DF3 customers from our older edge platform to our newer edge platform. This not only brings customers on to newer hardware, but it also brings them away from ageing patch panel infrastructure. It is important in this instance to note that customers may experience interface flaps while works are being performed even if they are not being moved in that moment. This is due to the level of intrusive works required to move customer connections. As a result please consider services to be at risk within these windows. It is also important to note that customers being moved over to this platform will no longer be part of our own STP instance and so customers will need to handle loop protection on their own infrastructure. Loops spotted on our network will have one port shut down to resolve the immediate loop potential and then those customers will be notified of the action at the end of the maintenance window. Customers that have BGP instances with us which are already on our core platform but receive L2 through our older edge will have one instance shut and moved to cleanly migrate them away and reduce impact. Customers that have BGP instances with us which are on our edge platform will have all sessions admin shut and then moved and re-established. Standard Flat and static route IPT services will but shut down unconfigured and then reconfigured on to the new platform. Backhaul services, protected or un-protected will be moved one at a time but will be affected in this window. In all cases our team will ensure that services look to have returned after migration before moving on to the next service. We will be moving customers one at a time within the window unless we have pre-agreed a time slot with you. For customers with a single feed we anticipate affected services will not have connectivity for 15 minutes and no more than 30 minutes unless we are required to roll back the service or perform troubleshooting. For customers with dual feed we anticipate affected services will not have connectivity for up to 30 minutes unless we are required to roll back the service or perform troubleshooting. Affected customers will require their cables to be shortened within our own infrastructure and so this will be done within the move, due to this you may see more than one interface flap as we will endeavour to bring services back up before disconnecting a single link one at a time to perform those L1 alterations. There are a large number of customer ports to migrate to the new platform so customers not affected in the first window should anticipate being affected in the second as we run sequentially though our infrastructure. For any remaining customers we will schedule a third window now (this one) however anticipate that we will be able to cancel it on Sun 20th July should everyone be migrated. For any questions or concerns regarding this maintenance please contact the NOC. This maintenance has been logged under [CDC-ID: #252886]

Metrics

Maidstone IP Core

100.00%




Dartford IP Core

100.00%




London IP Core

100.00%




Byfleet IP Core

100.00%




Maidstone IP Core

100.00%




Dartford IP Core

100.00%




London IP Core

100.00%




Byfleet IP Core

100.00%




Maidstone IP Core

100.00%




Dartford IP Core

100.00%




London IP Core

100.00%




Byfleet IP Core

100.00%