Webhosting

My apologies, i could not find it using the terms i used. I didn't know about them but proberly because of their/your recent entry web hosting market. I wish much success with your new venture in South Africa.

I must admit your domain prices for co.za are pretty reasonable, you could resell those you know, alot of hosting companies would pay some one for the simple service of registerng the domain.

Anyway welcome to South Africa! Where are your servers currently?
 
3x-a-d3-u5 said:
Sorry to stop the party...
Hetzner: Overpriced but good service with SLOW servers! (try pining it !)
Click to expand...

I tried pinging a couple of the hosts mentioned here:
Hetzner (DE): 322ms
Hetzner (Cpt): 231ms
serv.co.za: 381ms
texo.co.za: 399ms



realwebhosting.za.net: 404ms. :|​
 
Whoa -- what connection are you using?
I get a 50ms ping to hetzner.co.za and a 220ms ping to texo.co.za

(on SAIX ADSL)

ETA: and realwebhosting.za.net can't be found
 
Well if you were trying to ping realwebhosting.co.za they don't seem to exist, but if you were trying to ping www.realwebspace.za.net then i just got:
Reply from 208.101.45.117: bytes=32 time=387ms TTL=47
Reply from 208.101.45.117: bytes=32 time=387ms TTL=47
Reply from 208.101.45.117: bytes=32 time=389ms TTL=47
Reply from 208.101.45.117: bytes=32 time=385ms TTL=47
Reply from 208.101.45.117: bytes=32 time=387ms TTL=47
Reply from 208.101.45.117: bytes=32 time=388ms TTL=47
Reply from 208.101.45.117: bytes=32 time=388ms TTL=47
Reply from 208.101.45.117: bytes=32 time=389ms TTL=47
Reply from 208.101.45.117: bytes=32 time=385ms TTL=47

And from texo:
Reply from 72.34.41.100: bytes=32 time=486ms TTL=44
Reply from 72.34.41.100: bytes=32 time=488ms TTL=44
Reply from 72.34.41.100: bytes=32 time=489ms TTL=44
Reply from 72.34.41.100: bytes=32 time=488ms TTL=44
Reply from 72.34.41.100: bytes=32 time=487ms TTL=44
Reply from 72.34.41.100: bytes=32 time=489ms TTL=44
Reply from 72.34.41.100: bytes=32 time=488ms TTL=44
Reply from 72.34.41.100: bytes=32 time=489ms TTL=44

And from serv.co.za
Reply from 209.31.112.18: bytes=32 time=458ms TTL=50
Reply from 209.31.112.18: bytes=32 time=460ms TTL=50
Reply from 209.31.112.18: bytes=32 time=457ms TTL=50
Reply from 209.31.112.18: bytes=32 time=459ms TTL=50
Reply from 209.31.112.18: bytes=32 time=457ms TTL=50
Reply from 209.31.112.18: bytes=32 time=456ms TTL=50

But right now i don't agree with either of these results as i know that all these hosts are pretty fast. Its all about position though for instance if i was to ping an American IP fro,m Cape town, PE, Durban, Pretoria or Joburg you would get a different average resopnce time from each location even if it was the same ip and done simultaneously.

So the bottom line is :Ping what ever website you want to host with. If the price and ping is right go for it. :)
 
Last edited:
texo said:
Whoa -- what connection are you using?
Click to expand...

Grumble... don't even start me on that... :(

Point is, as a comparison, all of the other hosts are faster than realwebhosting.

I dunno, but if I was setting up a hosting business I'd shell out the R50 for a .co.za domain.
 
Grumble... don't even start me on that...

Point is, as a comparison, all of the other hosts are faster than realwebhosting.

I dunno, but if I was setting up a hosting business I'd shell out the R50 for a .co.za domain.
Click to expand...

Hi,

Even though realwebhosting (and the above) are competitors of mine, I just need to step in here quick:

Latency is not always relative to transfer speed
Lower Latency does not mean faster servers
Lower Latency does not always mean high uptime
Lower Latency does not always mean good service stability

I would much rather have a high quality host with a ping of 50 or even 100 ms higher (that you won't even notice in general when you are browsing) than a unreliable one but with a slightly less ping.

Best wishes

RavenServers
 
Pinging texo.co.za [72.34.41.100] with 32 bytes of data:

Reply from 72.34.41.100: bytes=32 time=452ms TTL=44
Reply from 72.34.41.100: bytes=32 time=453ms TTL=44
Reply from 72.34.41.100: bytes=32 time=452ms TTL=44
Reply from 72.34.41.100: bytes=32 time=451ms TTL=44

Ping statistics for 72.34.41.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 451ms, Maximum = 453ms, Average = 452ms


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

Reply from 196.22.142.41: bytes=32 time=42ms TTL=246
Reply from 196.22.142.41: bytes=32 time=43ms TTL=246
Reply from 196.22.142.41: bytes=32 time=44ms TTL=246
Reply from 196.22.142.41: bytes=32 time=43ms TTL=246

Ping statistics for 196.22.142.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 44ms, Average = 43ms

Pinging hetzner.de [213.133.105.162] with 32 bytes of data:

Reply from 213.133.105.162: bytes=32 time=441ms TTL=53
Reply from 213.133.105.162: bytes=32 time=442ms TTL=53
Reply from 213.133.105.162: bytes=32 time=441ms TTL=53
Reply from 213.133.105.162: bytes=32 time=441ms TTL=53

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


Pinging serv.co.za [209.31.112.18] with 32 bytes of data:

Reply from 209.31.112.18: bytes=32 time=420ms TTL=49
Reply from 209.31.112.18: bytes=32 time=420ms TTL=49
Reply from 209.31.112.18: bytes=32 time=420ms TTL=49
Reply from 209.31.112.18: bytes=32 time=420ms TTL=49

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


And then my own (international) host which will go unnamed:
Pinging <ip> with 32 bytes of data:

Reply from <ip>: bytes=32 time=356ms TTL=51
Reply from <ip>: bytes=32 time=356ms TTL=51
Reply from <ip>: bytes=32 time=358ms TTL=51
Reply from <ip>: bytes=32 time=358ms TTL=51

Ping statistics for <ip>:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 356ms, Maximum = 358ms, Average = 357ms


Pretty happy with that result :) :) :)

Good ping is one of the reasons for me choosing the upstream provider. One of the things that contributes to that low ping is a low amount of hops on a traceroute. They is basically 1 hop between the telkom router that side of the world and their network. I get 14 hops including my router and my adsl modem (2 hops/devices). If you're "pinging" to judge hosts then I'd recommend you also use "tracert" in windows or "traceroute" in linux which will show you exactly where it is that the latency is coming from.
 
They are not cheap and their package is way to small. They also dont specify the monthly transfer (that i can see)
 
I makes my pretty ill having to read all of this sales talk, and the jostling that is going on.

For my ping hetzner was the quickest by far, but i agree with Ravenwood that that is not all that counts. He is the only one here who is not trying to jocky for position. I wouldnt touch the rest of you with a 10 foot barge pole as your behavior is very amateurish.
 
Byrd hetzner.co.za would be the fastest as it's local. They give you much less bandwidth for the same price on their local options. It's not their fault of course, it's telkom's.
As for all the other webhosts etc there are ridiculously many out there. Some of them have a "spin" in some way or another but most are just dime-a-dozen reseller types...
 
stats, stats, stats. Do you buy a car just cause it's fast? It's nice to drive a 4L V8 that could do 1-100 in 5seconds, but do you know what you're going to fork out on fuel, tires & insurance?

Point is don't judge a host by it's ping time. I'm not going to try and win you as a client. This decision is yours and yours alone. But, I will give you some advice. Being in the developmeng & hosting business since 1999, I'v seen a lot, and I've tried out a lot of options. Here are a few things you should look at:
  • What kind of servers do they run on, and when last was the OS, control panel, additional software, kernel, etc updated?
  • Are they using some of the latest server technologies? a PIII is a good server, but it shouldn't be on the shelf anymore. Especially since you'll be sharing that server with 500 other websites. Unless you have enough money for your own dedicated server.
  • Do you really need unlimited space? NO ONE can offer you unlimited space. Period. There WILL be a catch, read the TOS & SLA a few times before signing up.
  • Where are the servers located? This doesn't really make a difference. Unless you need to give access via VPN to the server to your clients, from some JAVA app, you don't need something with 30ms response times. Instead look for someone with multilple peers connected to them, and who can offer 98% + network uptime.
  • Hardware RAID & offsite backups are a defenate must. The last thing you want is lost data due to failed hardware & no backups.
  • What kind of service do you need, and will you get? This is important, especially when there's downtime. I've heard of big companies "dissapearing" the moment there's something wrong. You don't want this.
  • And lastly, do you really need all those extras that you don't even know what it's for? Rather make sure you get what you need.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X