London Dedicated Servers – Data Center and Colo

OpenMetal for London Dedicated Servers 

OpenMetal has a wide range of enterprise dedicated servers available both as bare metal and within a hosted private cloud. For those looking for best dedicated servers for a London based business, we have two data center locations that can serve your purpose.

• Amsterdam, Netherlands
• Ashburn, Virginia

Pick the right dedicated server provider for London

Compare data center ping times for London

The following table and map shows the average ping times between London, Great Britain and OpenMetal’s data center locations in Amsterdam, Netherlands and Ashburn, United States. An additional 5 ms have been added to the observed average ping times in order to account for possible latency in the last mile, especially if not in a central area in London.

How to know when a data center location is a good choice 

Consider a data center location inappropriate if it fails to meet the following criteria:

• Latency Tests: If ping times consistently surpass 30 milliseconds (ms), this does not align with OpenMetal’s standards for contemporary cloud and hosting requirements.
• Geographical Proximity: If the location is significantly distant from the main user group, this could introduce additional delays.
• Infrastructure Quality: If the local infrastructure is inadequate in capacity or quality for ensuring low-latency connections.
• Connectivity Choices: If there are restricted or no direct links to major internet backbones or networks.

OpenMetal’s data centers, positioned in Tier III facilities with robust connections to key internet backbones, ensure that infrastructure quality and connectivity choices are up to standards. OpenMetal advises opting for locations where the latency, or ping time, is below 30 ms to support modern digital services. Given that the latency from London to our Ashburn data center center is more than 70 ms, this location would not be suitable for colocation or hosted IaaS solutions catering to the city of London.

OpenMetal’s facility in Amsterdam delivers extremely low latency, with an observed 8.268 ms maximum ping time from central London. After adding an extra 5 ms for the last mile for less central locations, the maximum ping time is 13.268 ms, which much better than the 30 ms threshold recommended by OpenMetal. This is great for applications that need low latency. For these types of services, Amsterdam’s location is the recommended choice for London colo, bare metal, hosted applications and cloud services.

If your business / customers are located in and around London, Great Britain, then OpenMetal’s data center location in Amsterdam, Netherlands, is the best data center for your London colocation alternative. 

OpenMetal bare metal dedicated servers and private clouds are hosted at a Digital Realty facility in Amsterdam, Netherlands, offering N+1 UPS power and cooling, sophisticated alarm and monitoring systems, and high-density power support. Positioned only 10 minutes from Schiphol Airport, the carrier-neutral site features energy-efficient design, runs entirely on renewable energy, and is a key hub for financial tech, energy, insurance, and consumer goods leaders. Read more.

Ping Times and Traceroutes from London to Amsterdam

The following shows the ping time from a centrally located looking glass in London, Great Britain to the OpenMetal dedicated server data center location in Amsterdam, Netherlands. There were 5 packets of data transmitted with the following ping time statistics:

• Minimum Ping Time: 7.888 ms
• Average Ping Time: 8.095 ms
• Maximum Ping Time: 8.799 ms

PING 213.165.229.4 (213.165.229.4) 56(84) bytes of data.
64 bytes from 213.165.229.4: icmp_seq=1 ttl=56 time=8.21 ms
64 bytes from 213.165.229.4: icmp_seq=2 ttl=56 time=7.88 ms
64 bytes from 213.165.229.4: icmp_seq=3 ttl=56 time=8.08 ms
64 bytes from 213.165.229.4: icmp_seq=4 ttl=56 time=8.01 ms
64 bytes from 213.165.229.4: icmp_seq=5 ttl=56 time=8.26 ms

--- 213.165.229.4 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 7.888/8.095/8.268/0.158 ms