Razor Servers
Top Rated Alternatives
See all Alternatives
Overall
Freshly obtained ping times (showing lots of packets lost) to Alpari US server (the picture is the same when pinging FXDD NY server, which tells me it's not Alpari or FXDD at fault here, but Razor Servers, who did not bother to send any announcement about maintenance or issues with their infrastructure):
>ping -t 208.122.38.253
Pinging 208.122.38.253 with 32 bytes of data:
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=6ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Request timed out.
Reply from 208.122.38.253: bytes=32 time=4ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=4ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Request timed out.
Reply from 208.122.38.253: bytes=32 time=4ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=4ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=4ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=4ms TTL=59
Request timed out.
Request timed out.
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Request timed out.
Reply from 208.122.38.253: bytes=32 time=4ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Request timed out.
Request timed out.
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Reply from 208.122.38.253: bytes=32 time=5ms TTL=59
Ping statistics for 208.122.38.253:
Packets: Sent = 38, Received = 31, Lost = 7 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 6ms, Average = 4ms
Overall
I'm using them for 8 months now, and here is my rating: Ease of Use: 5, Pricing: 10, Features: 7, Customer Service: 1.
I pay $20 / month for a 512 MB Hyper-V Win2K8 R2 machine, and being very close to my broker (10 ms), I like the setup. The problem is that I asked for an upgrade to 1 GB a couple of months ago. I used their ticketing system, then called them (twice, and left voice messages since no one would reply), then even used the "contact us" form on their webpage, which is typically used by prospective clients (I thought that would help make my request higher priority, or at least more visible).
Five months later I still did not get a reply, and as a matter of fact, my support tickets were closed with no explanation (I guess they automatically close after a while; I don't want to believe they were closed by the support staff without answering the simple request in there).
I gave a 1 (rather than 0) to the Customer Service because I had a conversation with them in Dec 2010, so I know they exist and reply to emails/tickets. But because I'm stuck with the current configuration I decided to decrease the Ease of Use to 5...
In case you want to open an account with them, ask about the plans of improving the Customer Service department, because other than that, this VPS provider is offering good value.
I hope this helps, and I wish you happy trading!
