Summary
- Crusoe completed the London public internet connection point for its eu-iceland1 region on 6 October.
- Iceland traffic previously used Amsterdam and Dublin; London now provides a third public route.
- Public IP addresses remained unchanged and customers were not required to modify DNS records or firewall rules.
Crusoe has added London as a third public internet connection point for its Iceland cloud region, expanding the routes available for traffic moving between eu-iceland1 and external networks.
The company completed the London work between 04:30 and 06:30 UTC on 6 October. Public internet traffic for eu-iceland1 had previously passed through Amsterdam and Dublin; after the maintenance, some traffic can also use London.
Crusoe said the change adds capacity and redundancy. Existing public IP addresses were unchanged, customers were not required to alter DNS records or firewall rules, and running workloads were expected to remain available throughout the maintenance window.
The network path taken by individual traffic flows can nevertheless change. Crusoe warned that latency to some destinations may shift slightly because packets can now traverse a different route, and asked customers to report packet loss, connection resets or large latency changes observed during or after the work.
A third route changes failure options
The additional connection gives Crusoe another option when it routes public traffic between Iceland and the wider internet. If one route becomes unavailable or congested, traffic can potentially use another path rather than depending on Amsterdam and Dublin alone.
The resilience gained from that change depends on the underlying physical topology. Separate logical routes can still share a subsea cable, landing station, terrestrial duct, carrier or network node. Where those common elements exist, several nominally independent paths can fail together.
Crusoe’s maintenance notice does not identify the full physical route behind the new London connection. The completed change therefore establishes an additional public internet path, but it does not prove that all three end-to-end routes are physically independent.
Iceland can offer abundant electricity and a cool climate for high-performance computing, but large compute clusters also depend on sufficient external network capacity to move data, software, storage traffic and service requests between the island and other markets.
A facility can have available power and installed accelerators while still being limited by the network if external links become congested or unavailable. Long-haul fibre capacity and route diversity consequently form part of the usable infrastructure around a compute region, particularly where customers operate workloads across several countries.
AI workloads can increase those requirements because training, inference and data processing may involve large transfers between storage platforms, compute clusters and customer environments. The proportion carried over the public internet varies by architecture, especially where customers use private connectivity, but the regional network must still support service traffic and external data movement.
London adds another major European network market to Crusoe’s public routing options. The practical effect is not a change in compute capacity inside eu-iceland1, but another location through which public traffic can enter or leave the region.
Keeping customer public IP addresses unchanged allows Crusoe to introduce the route below the application layer. Customers do not have to readdress services simply because the network has another connection point available for routing.
The maintenance was completed at 06:30 UTC on 6 October. Its operational value will depend on how Crusoe uses London alongside Amsterdam and Dublin, and on the extent to which the new route is physically diverse from the infrastructure already carrying Iceland traffic.
