Now the dedicated server is up and running I would like to get an idea of how well it is responding to users. Over here in Australia it takes a whopping ~375ms to ping the server. This is mainly because of a routing problem with the Telstra internet service.
All packets are being sent from Sydney to the West coast of America. The server is located in San Francisco and so the packets should then be routed straight over to the data center. But no, instead they are going all the way to the UK!!! Once they get to the UK they are sent straight back again to the West coast and only then are they sent on to the server. This is usually around 22 hops and so it’s not surprising the ping is so slow.
Could I ask people to spend 30 seconds using the ping command to see how long it takes to reach my new server. If you could post a comment with your location (city, country) along with the ping time that would be great. Just using the following command prompt…
ping www.componentfactory.com
Thanks!
April 25th, 2007 at 6:00 pm
From Heilbronn, Germany a ping tooks 222ms. But we have anly a DSL 2000 for 35 people in your company.
Greetings,
TretMine.
April 25th, 2007 at 6:17 pm
Pinging from Cheshire, UK (25/04/07, 09:12):
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 174ms, Average = 172ms
April 25th, 2007 at 6:38 pm
From Exmouth, United Kingdom my ping took on avg 178ms.
Regards
Lee
April 25th, 2007 at 7:08 pm
From Oxford, UK
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 182ms, Maximum = 183ms, Average = 182ms
April 25th, 2007 at 7:12 pm
From Telford, UK
Average ping was 160ms
April 25th, 2007 at 8:25 pm
From Lugano, Switzerland
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 192ms, Maximum = 193ms, Average = 192ms
April 25th, 2007 at 8:40 pm
From Harelbeke, Belgium:
Minimum = 165ms, Maximum = 172ms, Average = 168ms
April 25th, 2007 at 8:45 pm
From Raleigh NC, East Coast USA:
Approximate round trip times in milli-seconds:
Minimum = 80ms, Maximum = 89ms, Average = 83ms
April 25th, 2007 at 9:24 pm
From Cologne Germany:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 210ms, Maximum = 1556ms, Average = 546ms
April 25th, 2007 at 10:13 pm
From Toronto Canada
Reply from 208.96.52.211: bytes=32 time=82ms TTL=52
Reply from 208.96.52.211: bytes=32 time=80ms TTL=52
Reply from 208.96.52.211: bytes=32 time=83ms TTL=52
Reply from 208.96.52.211: bytes=32 time=78ms TTL=52
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 83ms, Average = 80ms
April 25th, 2007 at 10:21 pm
From Dallas, Texas, USA
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 83ms, Maximum = 85ms, Average = 84ms
April 26th, 2007 at 12:36 am
From York, UK
Reply from 208.96.52.211: bytes=32 time=178ms TTL=52
Reply from 208.96.52.211: bytes=32 time=176ms TTL=52
Reply from 208.96.52.211: bytes=32 time=178ms TTL=52
Reply from 208.96.52.211: bytes=32 time=178ms TTL=52
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 176ms, Maximum = 178ms, Average = 177ms
April 26th, 2007 at 1:11 am
From Port Orchard, WA
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 48.379/52.598/54.754/2.172 ms, pipe 2
Traceroute is nice as well:
traceroute to http://www.componentfactory.com (208.96.52.211), 30 hops max, 38 byte packets
1 192.168.101.1 (192.168.101.1) 0.404 ms 0.356 ms 0.181 ms
2 24.113.37.1 (24.113.37.1) 9.676 ms 11.072 ms 8.744 ms
3 24-113-127-41.wavecable.com (24.113.127.41) 10.716 ms 13.835 ms 9.096 ms
4 wavebroadband-gw.g11-0.oly-cor0.noanet.net (64.146.232.253) 11.285 ms 11.626 ms 11.387 ms
5 srp2-0.wtn-cor0.noanet.net (66.119.192.17) 15.779 ms 19.337 ms 17.153 ms
6 six.above.net (198.32.180.19) 26.692 ms 14.257 ms 19.515 ms
7 so-2-2-2.mpr1.sjc2.us.above.net (64.125.28.182) 41.375 ms 37.853 ms 32.943 ms
8 so-4-0-0.mpr1.sfo3.us.above.net (64.125.31.122) 33.725 ms 33.112 ms 38.569 ms
9 64.125.129.45.available.above.net (64.125.129.45) 51.722 ms 51.723 ms 60.115 ms
10 customer-reverse-entry.208.96.31.16 (208.96.31.16) 52.450 ms 48.705 ms 46.603 ms
11 http://www.componentfactory.net (208.96.52.211) 49.338 ms 51.681 ms 54.255 ms
six.above.net is the Seattle Internet Exchange, so you have good connectivity to the Seattle area.
April 26th, 2007 at 1:15 am
Denver, CO, US
— http://www.componentfactory.com ping statistics —
50 packets transmitted, 50 packets received, 0% packet loss
round-trip min/avg/max= 86.416/95.821/116.118ms
April 26th, 2007 at 1:35 am
From St. Louis, Missouri – United States
Ping statistics for 208.96.52.211:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Apporximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 137ms, Average = 79ms
Cheers!
April 26th, 2007 at 2:01 am
From Seattle Washington – United States
Reply from 208.96.52.211: bytes=32 time=44ms TTL=56
Reply from 208.96.52.211: bytes=32 time=44ms TTL=56
Reply from 208.96.52.211: bytes=32 time=49ms TTL=56
Reply from 208.96.52.211: bytes=32 time=52ms TTL=56
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 52ms, Average = 47ms
April 26th, 2007 at 3:18 am
From Bangkok Thailand
Pinging http://www.componentfactory.com [208.96.52.211] with 32 b
Reply from 208.96.52.211: bytes=32 time=813ms TTL=250
Reply from 208.96.xxx.xxx: bytes=32 time=1082ms TTL=250
Reply from 208.96.xxx.xxx: bytes=32 time=1004ms TTL=250
Reply from 208.96.xxx.xxx: bytes=32 time=1016ms TTL=250
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 813ms, Maximum = 1082ms, Average = 978ms
April 26th, 2007 at 5:09 am
From Belgium, Brussels:
Pinging http://www.componentfactory.com [208.96.52.211] with 32 bytes of data:
Reply from 208.96.52.211: bytes=32 time=167ms TTL=48
Reply from 208.96.52.211: bytes=32 time=168ms TTL=48
Reply from 208.96.52.211: bytes=32 time=168ms TTL=48
Reply from 208.96.52.211: bytes=32 time=168ms TTL=48
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 167ms, Maximum = 168ms, Average = 167ms
April 26th, 2007 at 6:07 am
From Raleigh, North Carolina, US
Min = 88ms, Max = 95ms, Avg = 91ms
April 26th, 2007 at 6:07 am
Surprise, AZ (outside Phoenix)
Pinging http://www.componentfactory.com [208.96.52.211] with 32 bytes of data:
Reply from 208.96.52.211: bytes=32 time=76ms TTL=49
Reply from 208.96.52.211: bytes=32 time=74ms TTL=49
Reply from 208.96.52.211: bytes=32 time=77ms TTL=49
Reply from 208.96.52.211: bytes=32 time=78ms TTL=49
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 78ms, Average = 76ms
April 26th, 2007 at 6:36 am
476ms average from Israel
April 26th, 2007 at 10:25 am
from tampa fl, usa on brighthouse / roadrunner cable:
Ping statistics for 208.96.52.211:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 81ms, Maximum = 117ms, Average = 84ms
April 26th, 2007 at 7:45 pm
Copenhagen, Denmark:
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 197ms, Maximum = 197ms, Average = 197ms
April 26th, 2007 at 8:34 pm
Paris, France
Ping statistics for 208.96.52.211
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 183ms, Maximum = 182ms, Average = 183ms
April 26th, 2007 at 8:38 pm
Hi, i’m in the UK and the results are…….
177ms Minimum, 181ms Max with an average of 179ms :)
April 27th, 2007 at 2:14 am
Brescia , Italy
Pinging http://www.componentfactory.com [208.96.52.211] with 32 bytes of data:
Reply from 208.96.52.211: bytes=32 time=209ms TTL=49
Reply from 208.96.52.211: bytes=32 time=209ms TTL=49
Reply from 208.96.52.211: bytes=32 time=210ms TTL=49
Reply from 208.96.52.211: bytes=32 time=208ms TTL=49
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 208ms, Maximum = 210ms, Average = 209ms
April 27th, 2007 at 2:33 am
202ms from Warsaw, Poland
April 27th, 2007 at 5:14 am
53ms from Fort Smith, AR, USA
April 28th, 2007 at 2:55 am
Opole, Poland
Minimum = 206ms, Maximum = 216ms, Average = 210ms
April 28th, 2007 at 9:35 pm
Hong Kong, China
Ping statistics for 208.96.52.211:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 205ms, Maximum = 232ms, Average = 222ms