Fastest Web Hosts

A

Andrewc

Well-Known Member
Joined
Oct 26, 2005
Messages
327
Reaction score
0
Location
The net
Ok lets do a little test to find out who is the fastest web host.

Try ping your web hosts site or your site and post the result on this thread.

notice the time=**ms

"Ping time" refers to the amount of time it takes for a small "packet" of data to travel over the internet from one computer to another computer and back to the first computer. It is usually reported in milliseconds (ms).
Click to expand...


So the lower ping time the faster the web host :)
 
Last edited:
I'm not my target audience so it doesnt really matter what my ping times are.

EDIT - Is there a service that would let me ping my host remotely? Below is the reason why I ask - ping via uunet/verizon:

Ping has started ...

PING ns2.powweb.com (66.152.97.4): 56 data bytes
64 bytes from 66.152.97.4: icmp_seq=0 ttl=48 time=4123.396 ms
64 bytes from 66.152.97.4: icmp_seq=1 ttl=48 time=4213.762 ms
64 bytes from 66.152.97.4: icmp_seq=5 ttl=48 time=4141.450 ms
64 bytes from 66.152.97.4: icmp_seq=8 ttl=48 time=3787.838 ms

--- ns2.powweb.com ping statistics ---
10 packets transmitted, 4 packets received, 60% packet loss
round-trip min/avg/max/stddev = 3787.838/4066.611/4213.762/164.464 ms
 
Last edited:
Web Africa from 512K line

Pinging www.webafrica.co.za [196.31.65.20] with 32 bytes of data:

Reply from 196.31.65.20: bytes=32 time=80ms TTL=114
Reply from 196.31.65.20: bytes=32 time=70ms TTL=114
Reply from 196.31.65.20: bytes=32 time=71ms TTL=114
Reply from 196.31.65.20: bytes=32 time=70ms TTL=114

Ping statistics for 196.31.65.20:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 80ms, Average = 72ms
 
Last edited:
Hetzner from 512K line

Pinging www.hetzner.co.za [196.7.147.101] with 32 bytes of data:

Reply from 196.7.147.101: bytes=32 time=70ms TTL=241
Reply from 196.7.147.101: bytes=32 time=120ms TTL=241
Reply from 196.7.147.101: bytes=32 time=71ms TTL=241
Reply from 196.7.147.101: bytes=32 time=70ms TTL=241

Ping statistics for 196.7.147.101:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 70ms, Maximum = 120ms, Average = 82ms
 
Afrihost from 512k line

Pinging www.afrihost.co.za [196.35.64.184] with 32 bytes of data:

Reply from 196.35.64.184: bytes=32 time=60ms TTL=55
Reply from 196.35.64.184: bytes=32 time=60ms TTL=55
Reply from 196.35.64.184: bytes=32 time=50ms TTL=55
Reply from 196.35.64.184: bytes=32 time=40ms TTL=55

Ping statistics for 196.35.64.184:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 60ms, Average = 52ms
 
Backbone IT Solutions from 512K line

Pinging www.backboneit.co.za [196.22.132.136] with 32 bytes of data:

Reply from 196.22.132.136: bytes=32 time=60ms TTL=241
Reply from 196.22.132.136: bytes=32 time=40ms TTL=241
Reply from 196.22.132.136: bytes=32 time=50ms TTL=241
Reply from 196.22.132.136: bytes=32 time=50ms TTL=241

Ping statistics for 196.22.132.136:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 40ms, Maximum = 60ms, Average = 50ms
 
webonline from a 512k (edit: saol account)

C:\Documents and Settings\>ping webonline.co.za

Pinging webonline.co.za [196.7.217.137] with 32 bytes of data:

Reply from 196.7.217.137: bytes=32 time=36ms TTL=248
Reply from 196.7.217.137: bytes=32 time=39ms TTL=248
Reply from 196.7.217.137: bytes=32 time=40ms TTL=248
Reply from 196.7.217.137: bytes=32 time=39ms TTL=248

Ping statistics for 196.7.217.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 40ms, Average = 38ms
 
Last edited:
This is what I get..

Pinging webonline.co.za [196.7.217.137] with 32 bytes of data:

Reply from 196.7.217.137: bytes=32 time=60ms TTL=242
Reply from 196.7.217.137: bytes=32 time=50ms TTL=242
Reply from 196.7.217.137: bytes=32 time=50ms TTL=242
Reply from 196.7.217.137: bytes=32 time=60ms TTL=242

Ping statistics for 196.7.217.137:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 60ms, Average = 55ms
 
gamco from 512k saol account

C:\Documents and Settings\>ping gamco.co.za

Pinging gamco.co.za [196.35.164.204] with 32 bytes of data:

Reply from 196.35.164.204: bytes=32 time=44ms TTL=118
Reply from 196.35.164.204: bytes=32 time=47ms TTL=118
Reply from 196.35.164.204: bytes=32 time=47ms TTL=118
Reply from 196.35.164.204: bytes=32 time=69ms TTL=118

Ping statistics for 196.35.164.204:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 69ms, Average = 51ms
 
Pinging www.telkomsa.net [196.25.211.40] with 32 bytes of data:

Reply from 196.25.211.40: bytes=32 time=196ms TTL=123
Reply from 196.25.211.40: bytes=32 time=150ms TTL=123
Reply from 196.25.211.40: bytes=32 time=123ms TTL=123
Reply from 196.25.211.40: bytes=32 time=115ms TTL=123

Ping statistics for 196.25.211.40:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 115ms, Maximum = 196ms, Average = 146ms



Nuff said
 
I have a problem with using "ping" to test a web host. I am not taking a dig at you Andrew in any way here but using you as an example. What is to say that your web page is even hosted on the same server as those that you clients will be hosted on. For all we know the web host's web page could be in an entirely different data centre or network backbone. A better reflection would be the ping times of clients web sites that are in fact hosted on the server which will be provided for customer use.
 
What is the point of this?
1. Ping times don't show throughput (ie, a better test would be to download a 100mb file). It doesn't help you much if your latency is 5ms, but the server only has 64Kbits bandwidth!

2. These pings are from different locations, different networks etc. Doing things this way requires you to take into consideration things like congestion, contention ratios and router hops (look at the TTL values). If you want to test latency, find a common point with lots of free bandwidth (like dnsstuff.com)
 
Yes we are resellers of Hetzner but with slightly different packages ;)

We have our own server with Hetzner
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X