Tunnel server selection is important when ordering Core Transit services to ensure the best possible performance of your ethernet anywhere or basic tunnel services. 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 data center 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 tunnel server hubs from your site. The lowest latency will produce the best experience in nearly all cases.
How to Test
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 to use the ping command to test the latency to each site. A sample test to the Dallas site is shown below.
- The tunnel server with the lowest latency (response time) will be the best site.
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=54The full list of tunnel servers and host names are listed below:
| City | Hostname |
|---|---|
| Dallas (DFW1) | peering1.dfw.1.coretransit.io |
| Los Angelos (LAX1) | peering1.lax.1.coretransit.io |
If you still have tunnel server selection questions or other technical questions be sure to reach out to us!