Ping from corporate.singnet.com.sg to http://www.futurequest.net

PING http://www.futurequest.net (63.95.221.116): 56 data bytes
64 bytes from 63.95.221.116: icmp_seq=0 ttl=240 time=267.797 ms
64 bytes from 63.95.221.116: icmp_seq=1 ttl=240 time=268.926 ms
64 bytes from 63.95.221.116: icmp_seq=2 ttl=240 time=268.130 ms
64 bytes from 63.95.221.116: icmp_seq=3 ttl=240 time=281.148 ms
64 bytes from 63.95.221.116: icmp_seq=4 ttl=240 time=270.800 ms

--- http://www.futurequest.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 267.797/271.360/281.148/5.003 ms


Ping from corporate.singnet.com.sg to http://www.hosting4less.com

PING http://www.hosting4less.com (208.178.1.21): 56 data bytes
64 bytes from 208.178.1.21: icmp_seq=0 ttl=241 time=403.457 ms
64 bytes from 208.178.1.21: icmp_seq=1 ttl=241 time=404.708 ms
64 bytes from 208.178.1.21: icmp_seq=2 ttl=241 time=405.010 ms
64 bytes from 208.178.1.21: icmp_seq=4 ttl=241 time=404.783 ms

--- http://www.hosting4less.com ping statistics ---
5 packets transmitted, 4 packets received, 20% packet loss
round-trip min/avg/max/stddev = 403.457/404.490/405.010/0.606 ms

Traceroute from corporate.singnet.com.sg to http://www.futurequest.net

1 fe-3-0-0-newton (165.21.6.101) 0.740 ms 0.656 ms 0.406 ms
2 GE-1-1-0.bedok.singnet.com.sg (165.21.12.1) 1.146 ms 0.799 ms 1.033 ms
3 POS2-0.tp-core1.ix.singtel.com (202.160.250.53) 0.995 ms 0.943 ms 0.900 ms
4 202.160.250.6 (202.160.250.6) 1.179 ms 1.660 ms 1.207 ms
5 Serial0-0-0.paix-peer1.ix.singtel.com (202.160.255.214) 213.828 ms 221.938 ms 205.255 ms
6 pa-qwest.explorer.ix.singtel.com (203.127.108.194) 210.055 ms 213.648 ms 221.089 ms
7 sjo-core-02.inet.qwest.net (205.171.22.65) 211.976 ms 213.639 ms 208.646 ms
8 hou-core-02.inet.qwest.net (205.171.5.145) 279.352 ms 251.131 ms 260.272 ms
9 hou-core-01.inet.qwest.net (205.171.23.1) 252.029 ms 254.650 ms 251.911 ms
10 iah-core-01.inet.qwest.net (205.171.5.3) 267.600 ms 247.759 ms 252.410 ms
11 205.171.31.2 (205.171.31.2) 244.527 ms 262.698 ms 245.028 ms
12 tpa-core-03.inet.qwest.net (205.171.5.105) 270.708 ms 286.751 ms 285.528 ms
13 tpa-edge-03.inet.qwest.net (205.171.27.30) 280.188 ms 275.809 ms 263.846 ms
14 63.144.0.106 (63.144.0.106) 275.776 ms 302.338 ms 276.333 ms
15 futurequest.net (63.95.221.116) 267.926 ms 268.601 ms 267.828 ms




Traceroute from corporate.singnet.com.sg to http://www.hosting4less.com

1 fe-3-0-0-newton (165.21.6.101) 0.770 ms 0.679 ms 1.058 ms
2 GE-1-1-0.bedok.singnet.com.sg (165.21.12.1) 0.817 ms 0.974 ms 0.876 ms
3 POS2-0.tp-core1.ix.singtel.com (202.160.250.53) 1.242 ms 0.780 ms 0.734 ms
4 203.208.154.70 (203.208.154.70) 189.423 ms 209.919 ms 209.283 ms
5 p3-0.snjpca1-cr5.bbnplanet.net (4.24.238.1) 215.954 ms 209.613 ms 189.413 ms
6 p3-0.snjpca1-br1.bbnplanet.net (4.24.9.141) 199.754 ms 237.395 ms 227.256 ms
7 p10-0.lsanca2-br1.bbnplanet.net (4.24.8.26) 256.672 ms 220.963 ms 194.568 ms
8 p15-0.lsanca2-br2.bbnplanet.net (4.24.5.46) 195.767 ms 199.504 ms 199.133 ms
9 p7-0.lsanca1-ba2.bbnplanet.net (4.24.4.37) 204.662 ms 198.103 ms 194.347 ms
10 ATM2-0.BR1.LAX9.ALTER.NET (137.39.52.81) 197.313 ms 198.462 ms 195.497 ms
11 0.so-0-1-0.XL2.LAX9.ALTER.NET (152.63.113.18) 197.633 ms 225.116 ms 201.100 ms
12 152.63.115.165 (152.63.115.165) 209.889 ms 199.425 ms 196.692 ms
13 290.ATM7-0.XR2.LAX2.ALTER.NET (152.63.112.101) 212.337 ms 203.697 ms 203.812 ms
14 194.ATM5-0.GW4.LAX2.ALTER.NET (152.63.113.125) 198.824 ms 199.351 ms 203.720 ms
15 point1-gw.customer.alter.net (157.130.236.54) 404.212 ms 404.011 ms 403.456 ms
16 hosting4less.com (208.178.1.21) 403.776 ms 402.234 ms 402.676 ms

Generally, the ping to futurequest.net is about 150ms faster. Does this make a big difference?

Another thing is what do you guys look for in traceroute? Kindly share your knowledge.

Aaron

One thing to keep in mind, a 5 ping set does not necessarily reflect how well a host is performing. You should generally try to ping a host 100 times (oe more) to get an accurate reflection. You can do this on a Windows box by using -n:

ping -n 100 http://www.futurequest.net

If you are using a web based interface, you should find one that allows more then 5 pings.

In my opinion, yes, 150 ms does make a difference. Especially when you are talking about the accessibility of your website.

As far as the traceroutes, both show that the companies are on tier 1 backbones. Futurequest is hosted off Qwest's and hosting4less is off of UUNET's. Both Qwest and UUNET have excellent backbones.

You can also try using a GUI version of tracert, for example NeoTrace (www.neotrace.com).

Or even some kind of combined tool, CyberKit is quite usefel. ( http://www.cyberkit.net )

In any case, your ping times to both these hosts are not that good.