Honestly, I wish servercomplete was in the EU, or had an equal EU provider. If they had, id of picked up 5 of those special offer nehelem servers, even if they were just to wait for a while until I had an actual use for them all
I've got one just sitting aside unused right now (basic setup but with 2 1TB SATA III's set up in RAID). Couldn't pass up the price. I'm sure I'll figure out something to do with it (heck, the Dr. Office I do work for is wanting to set up a web site - maybe I'll host it there and recoup my costs - as well as being able to run a site or two for myself from it
).
I can't complain about the ping times. As you can see, I'm getting about the same to cnet.com - so the holdup is my ISP.
Tracys-Mac-mini:website tracy$ ping twowheeldemon.com
PING twowheeldemon.com (199.48.164.159): 56 data bytes
64 bytes from 199.48.164.159: icmp_seq=0 ttl=53 time=79.824 ms
64 bytes from 199.48.164.159: icmp_seq=1 ttl=53 time=70.418 ms
64 bytes from 199.48.164.159: icmp_seq=2 ttl=53 time=78.118 ms
Tracys-Mac-mini:website tracy$ ping cnet.com
PING cnet.com (64.30.224.118): 56 data bytes
64 bytes from 64.30.224.118: icmp_seq=0 ttl=241 time=79.698 ms
64 bytes from 64.30.224.118: icmp_seq=1 ttl=241 time=77.045 ms
64 bytes from 64.30.224.118: icmp_seq=2 ttl=241 time=74.589 ms
And when pinged from my VPS at RamNode
$ ping twowheeldemon.com
PING twowheeldemon.com (199.48.164.159) 56(84) bytes of data.
64 bytes from twowheeldemon.com (199.48.164.159): icmp_req=1 ttl=58 time=6.40 ms
64 bytes from twowheeldemon.com (199.48.164.159): icmp_req=2 ttl=58 time=6.38 ms
64 bytes from twowheeldemon.com (199.48.164.159): icmp_req=3 ttl=58 time=6.40 ms
64 bytes from twowheeldemon.com (199.48.164.159): icmp_req=4 ttl=58 time=6.37 ms