If you're ok with Linux systems, I can recommend Linode hosting (specifically their Newark servers). I trade using Python and I'm able to get ~2.5ms pings to both IB's market data and order routing servers. In case you do decide to use Linode - here's my referral link https://www.linode.com/?r=5453d6ae1c2be5da89a557ef54a514dfe8eda90c
Why is www.chicagovps.net so cheap? Are they legit.. I called rackspace the other day and they gave me a quote that is about 10 times this price (off course its more cores & memory). If I want to run a Linux based system, what kind of access would then give me. I don't want ports 80 or 443 exposed to the net. SSH should be good enough... how does the connectivity part work here?
May I ask why you don't want to host your own server? When I was looking for colo to trade futures, I found Steadfast. I spoke to Jeremy who was extremely helpful. They have 10g to Aurora. https://www.steadfast.net/why-steadfast/our-data-centers-network/data-centers
What IPs are you trying to reach in Chicago that you need fast/low latency to? The reason why I ask, we keep seeing more and more dedicated server & colocation sales from some of the people on here.
What kind of CPU and RAM configuration do you recommend? And which datacenter did you choose for your Linode VPS? Thanks!
IB uses level3 which was purchased by centurylink. Centurylink peers directly with many networks in their Chicago datacenter. Here are some pings from various networks/providers. The lowest latency connections (other than hosting at centurylink) is steadfast and colocrossing. centurylink: CHICAGO IL USA Ping results for: 8.17.22.31 (8.17.22.31) Target: 8.17.22.31 with 64 data bytes Success rate sent/received = (1/1) packets Round-Trip min/avg/max = 0ms/0ms/0ms cogent: PING cdc1.ibllc.com (8.17.22.31) 56(84) bytes of data. 64 bytes from 8.17.22.31 (8.17.22.31): icmp_seq=1 ttl=249 time=2.04 ms 64 bytes from 8.17.22.31 (8.17.22.31): icmp_seq=2 ttl=249 time=2.23 ms 64 bytes from 8.17.22.31 (8.17.22.31): icmp_seq=3 ttl=249 time=2.27 ms 64 bytes from 8.17.22.31 (8.17.22.31): icmp_seq=4 ttl=249 time=2.06 ms colocrossing: PING cdc1.ibllc.com (8.17.22.31) 56(84) bytes of data. 64 bytes from 8.17.22.31: icmp_seq=1 ttl=247 time=3.13 ms 64 bytes from 8.17.22.31: icmp_seq=2 ttl=247 time=1.78 ms 64 bytes from 8.17.22.31: icmp_seq=3 ttl=247 time=1.66 ms 64 bytes from 8.17.22.31: icmp_seq=4 ttl=247 time=1.62 ms ntt.net: Router: Chicago, IL - US Command: ping ip cdc1.ibllc.com Sending 5, 100-byte ICMP Echos to 8.17.22.31, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/2 ms telia-coresite: --- 8.17.22.31 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max/stddev = 2.108/2.227/2.416/0.113 ms fdcservers.net: --- 8.17.22.31 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4006ms rtt min/avg/max/mdev = 2.072/2.154/2.251/0.060 ms gthost.com: --- 8.17.22.31 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3008ms rtt min/avg/max/mdev = 1.853/2.031/2.183/0.138 ms vultr.com --- 8.17.22.31 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 7ms rtt min/avg/max/mdev = 1.941/2.004/2.072/0.057 ms steadfast: --- cdc1.ibllc.com ping statistics --- 10 packets transmitted, 10 received, 0% packet loss, time 9003ms rtt min/avg/max/mdev = 0.636/0.781/0.921/0.096 ms