Quite interesting, what is the difference between VPS.NET and Linode?

I'm trying to ping from Singapore VPS.NET Server in Tokyo (tokyo.vps.net) and Linode (tokyo1.linode.com) and the results are:

For Linode
64 bytes from tokyo1.linode.com (106.187.33.12): icmp_seq=1 ttl=57 time=81.4 ms
64 bytes from tokyo1.linode.com (106.187.33.12): icmp_seq=2 ttl=57 time=84.7 ms
64 bytes from tokyo1.linode.com (106.187.33.12): icmp_seq=3 ttl=57 time=81.0 ms
64 bytes from tokyo1.linode.com (106.187.33.12): icmp_seq=4 ttl=57 time=84.2 ms



For VPS.NET
64 bytes from 173.193.197.38-static.reverse.softlayer.com (173.193.197.38): icmp_seq=1 ttl=49 time=279 ms
64 bytes from 173.193.197.38-static.reverse.softlayer.com (173.193.197.38): icmp_seq=2 ttl=49 time=267 ms
64 bytes from 173.193.197.38-static.reverse.softlayer.com (173.193.197.38): icmp_seq=3 ttl=49 time=276 ms
64 bytes from 173.193.197.38-static.reverse.softlayer.com (173.193.197.38): icmp_seq=4 ttl=49 time=268 ms


you may try it here: http://www.speedtest.com.sg/speedtest.php

So, Linode is the winner.

Interesting to here what else makes the difference.


Thanks.

A quick look at a traceroute/mtr to that host would have taken you clear to Washington, D.C. So these results are not surprising. :p

It looks like they have a wildcard DNS entry that points *.vps.net (including tokyo.vps.net) to 173.193.197.38. Instead of inventing hostnames by prepending "tokyo" to their domain name, ask the vps.net folks to provide you with the IP address of a machine actually located in Tokyo.