Tunnel Server Selection Guide

Tunnel Server Selection Guide

Choosing a data center to consume your Core Transit Static IP Anywhere or other tunnel service is important to ensure the best possible performance.  The key consideration is latency, the time it takes for a data packet to travel from your location to its end destination.  Core Transit services are located in key internet hub locations around the US. The most latency will be from your end site to Core Transit vs Core Transit to your final internet destination.  That latency test will indicate the time it takes for data to get to our various data center hubs from your site.  The lowest latency will produce the best experience in nearly all cases.

Testing the latency to Core Transit is a simple process using the “ping” command. 

On a Windows computer tap the Windows Key + R together.

Type “cmd” into the run dialog box that opens. 

You will want then to type the command ping <site address> and record the results.  The site hostname address is listed at the end of this document. 

Example 1.

C:\>ping peering1.dfw1.coretransit.io

Pinging peering1.dfw1.coretransit.io [216.146.19.255] with 32 bytes of data:
Reply from 216.146.19.255: bytes=32 time=49ms TTL=54

After testing the data centers geographically closest to you, note the lowest latency, which would be your preferred site.