Welcome to WebmasterWorld Guest from 22.214.171.124
Forum Moderators: phranque
Pinging webmasterworld.com [126.96.36.199] with 32 bytes of data:
Reply from 188.8.131.52: bytes=32 time=137ms TTL=53
Reply from 184.108.40.206: bytes=32 time=129ms TTL=53
Reply from 220.127.116.11: bytes=32 time=128ms TTL=53
Reply from 18.104.22.168: bytes=32 time=126ms TTL=53
Ping statistics for 22.214.171.124:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 126ms, Maximum = 137ms, Average = 130ms
Tracing route to webmasterworld.com [126.96.36.199]
over a maximum of 30 hops:
4 105 ms 102 ms 104 ms ins-core1-atm5-1.desm.netINS.net [188.8.131.52]
5 115 ms 112 ms 113 ms 901.Hssi4-0.GW1.MSP1.ALTER.NET [184.108.40.206]
6 122 ms 122 ms 121 ms 151.ATM1-0.XR2.CHI4.ALTER.NET [220.127.116.11]
7 120 ms 121 ms 120 ms 190.ATM7-0.XR2.CHI6.ALTER.NET [18.104.22.168]
8 122 ms 125 ms 124 ms 190.ATM9-0-0.GW2.CHI6.ALTER.NET [22.214.171.124]
9 128 ms 125 ms 124 ms UU-ds3.axxs.net [126.96.36.199]
10 130 ms 129 ms 129 ms webmasterworld.com [188.8.131.52]
Notice that anything slow isn't with the server system, it is all before the system.
I think this might be just what you're looking for.
From my experience, pings, tracert or any other remote query to a server will only give you bandwidth measurement as there is no way to tell how fast the server served up the pages.
In order to get server performance numbers you have to have a server compoonent running on the server and you must have access to that component.
Addendum: a ping ms result varies with your connection to the net. 56K will result in bigger ms numbers than say T1.
That said, here is a home spun page of high q resources for various server/hosting stuff. Looks like a legit page (not one of those raided odp pages we've gotten used to seeing)