I bought a Basic VPS. Everything is great, but there's one problem: I've got only... ~200MHz of CPU to use. I can't do anything, because server will get laggy or crash. I don't think that's normal for $10 VPS to have only 200MHz of CPU - for ex. on my old VPS in VPSSquad.com I had almost full cpu to use, and it was for only $4 a month. Support isn't too good, maybe because I'm European, but it should be faster. Please, give us more of CPU, because VPS with 100gb disk, 768 MB ram and with 200MHz's CPU is pathetic and currently I spent $10 for very slow VPS. Sorry for posting it here, but I already sent a ticket on your website almost 6 hours ago and there's no reply. Maybe you will do something with it by reading it here. I can say that FTNHosting.net is really good at this price - but the CPU's speed makes it bad. If you use scripts-that-dont-use-too-much-cpu - get it... Thanks, Krzysztof. Edit: After my ticket - I've got better CPU's speed now. So - right now I can say it's best VPS hosting I ever seen for this price.
Oh... Big pings started... From yesterday to now I've got really big pings on my VPS in FTNHosting.net. It's above 1000ms. I contacted support, but they told me that it's a temporary routing between me and this server. But - all my friends got the same pings. If I'm using ping command on this VPS, pings sux too. For example, here's ping result from my VPS to digitalpoint: drakenet:~# ping www.digitalpoint.com PING crystalmethod.digitalpoint.com (216.9.35.56) 56(84) bytes of data. 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=3 ttl=50 time=177 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=1 ttl=50 time=2900 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=2 ttl=50 time=1901 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=4 ttl=50 time=2916 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=5 ttl=50 time=3578 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=6 ttl=50 time=3665 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=7 ttl=50 time=2766 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=8 ttl=50 time=3030 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=11 ttl=50 time=186 ms 64 bytes from crystalmethod.digitalpoint.com (216.9.35.56): icmp_seq=9 ttl=50 time=2510 ms --- crystalmethod.digitalpoint.com ping statistics --- 11 packets transmitted, 10 received, 9% packet loss, time 26581ms rtt min/avg/max/mdev = 177.468/2363.451/3665.716/1188.472 ms, pipe 3 Code (markup): Really strange. Please, dont close my support tickets, but do something with it. It isn't a temporary routing problem as you can see.
DigitalPoint forums is not a support center, it is a problem with YOUR ISP. You have pinged DigitalPoints server which is 5800 miles from the vps node which you are on which in return causes that high ping because of the distance, learn about how things work before you make false claims.
Moved to a new thread under webhosting because the posts above do not relate to the sales thread where they were initially posted. FreeTheNoob has requested that you use his support ticket system however it is still valid to ask in this thread.
I'm able to ping FTNHosting's website with ~100 ms ping and I am in the United States. That is good considering that their servers are in Germany.
VPSes are very expensive to run. If you're on a Dual Quad Core that is usually around 2.4ghz so that's 12 VPSes on equal share. But most companies would put that equal share per core (although 48 VPSes on one node is way too much). Basically if you want something fast you get more CPU on shared hosting. If you need root access and the freedom of a VPS you should quadruple your budget at least. It's not really fair to complain about a low CPU share on a VPS when you're only paying $10. But looks like they allocated you more CPU so you are extremely lucky to get so much for so little.
I agree @MickeyFinn ... Your LUCKY However, the high pings could be due to a ddos attack maybe? Its just a thought regards, Ryan