We’re migrating customer cloud servers that are currently hosted at all ‘edge’ locations to ‘core’ locations. Additionally, we’re launching, upgrading and decommissioning some ‘core’ network locations, where the bulk of customer data and servers are hosted.
Our edge locations are inside carrier hotels and prominently connected facilities. These are designed to handle network ingress & egress, CDN & DNS acceleration, streaming relays and DDoS mitigation. Such services are redundant by design, meaning a disaster at any single edge location will not affect the network as a whole.
However, we also offer cloud servers to be deployed at some edge locations, and recently suffered edge hardware failure that affected some of these customer cloud servers. Sadly, we can’t increase resiliency at edge locations due to capacity and power constraints, so we’ll migrate all cloud servers from edge to core locations instead.
Separately, last week we had a simultaneous network failure across two core locations that induced a period of downtime for some customers. Whilst we have N+1 redundant and resilient systems in all core locations, we’ll transition to N+2 to prevent recurrence of such network failures. This will involve the closure and merging of some core locations due to their locality, power and carrier availability.
All cloud servers currently hosted in edge locations will be seamlessly migrated to their nearest core location. This will be completed with ~20 seconds downtime, no data loss and no IP address changes. Most core locations being decommissioned/merged will also follow the same routine, with some exceptions. We will contact excepted customers directly to implement a plan of action.
UK-RDG1
Type: Core
Action: Decommission, merge with uk-wlv1 and uk-cov1
Impact: ~20 seconds downtime during IP address reroute
Timeline: June 2022
UK-LON1
Type: Edge
Action: Decommission
Impact: None - transit shift to uk-lon2
Timeline: June 2022
UK-LON3
Type: Core
Action: Decommission, merge with uk-wlv1 and uk-cov1
Impact: ~20 seconds downtime during IP address reroute
Timeline: June 2022
US-IN-SBN1
Type: Core
Action: Decommission, merge with us-ny-buf1 & us-mo-kcm1
Impact: ~20 seconds downtime during IP address reroute, some native IPs will be reissued
Timeline: June 2022
DE-FRA3
Type: Edge
Action: Decommission
Impact: None - replaced by de-fra1 & de-fra2
Timeline: July 2022
AU-SYD2
Type: Core
Action: Launch, merge with au-syd1 edge
Impact: ~20 seconds downtime during IP address reroute
Timeline: July 2022
US-CA-FMT1
Type: Edge & Core
Action: Decommission, merge with us-ca-los2, transit shift to us-ca-sjc1
Impact: ~20 seconds downtime during IP address reroute, some native IPs will be reissued
Timeline: July 2022
US-WA-SEA1
Type: Edge & Core
Action: Decommission and transfer of data to us-ca-los2, remain as edge only
Impact: ~20 seconds downtime during IP address reroute
Timeline: July 2022
US-TX-DAL1
Type: Edge & Core
Action: Decommission and transfer of data to us-mo-kcm1, remain as edge only
Impact: ~20 seconds downtime during IP address reroute
Timeline: August 2022
US-FL-MIA1
Type: Edge & Core
Action: Decommission and transfer of data to us-mo-kcm1, remain as edge only
Impact: ~20 seconds downtime during IP address reroute
Timeline: August 2022
US-CA-LOS1
Type: Edge & Core
Action: Decommission and transfer of data to us-ca-los2, transit shift to us-ca-los2 & us-ca-los3
Impact: ~20 seconds downtime during IP address reroute
Timeline: August 2022
US-CA-LOS3
Type: Edge & Core
Action: Decommission and transfer of data to us-ca-los2, remain as edge only
Impact: ~20 seconds downtime during IP address reroute
Timeline: September 2022
US-MO-KCM2
Type: Edge & Core
Action: Launch new edge & core, merge with us-mo-kcm1
Impact: None
Timeline: September 2022
No. Although we’ll decommission/merge some edge locations, we’ll still retain a presence in those locations. CDN, DNS, streaming and other edge services will be unaffected. We’ll also be launching new edge locations this year, including UAE and Taiwan.
Where cloud servers can be seamlessly transferred, we’ll do this automagically during off-peak periods, with no required intervention. Where IP address or other service-affecting changes will be required, we’ll reach out to implement a plan of action.
If you have any questions, please open a support ticket or email support@cloudunboxed.com.
Thanks you for your understanding.
