Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
The IPs are on CQG's technical specifications document. (https://www.cqg.com/Docs/CQGNETTechSpec.pdf) Did you use an IP geolocator? I found your discovery quite disturbing, so I followed up and tried a few geolocators and everything indicated Chicago as well. (Not barring the impossibility that it takes 67ms for light to travel between antipodes, making the 2ms ping rate from my server to Colorado theoretically impossible.)
Can you help answer these questions from other members on NexusFi?
I have multiple servers in Chicago. Everything is <1ms ping in Chicago datacenters near Aurora when I test against multiple brokers I use.
But your IP's are 20ms pings - indicating they are far, far outside of Chicago.
Yes, IP locator also indicates not in Illinois, but Colorado. These are not always reliable by themselves, but in combination with a 20ms ping, it is not Chicago.
1. Indeed, the IP lookup site you've provided suggests that my Washington D.C. server is in Colorado, and my Chicago server is in Texas (grossly inaccurate).
2. I reiterate that those are CQG's Chicago server IP addresses, as specified by CQG's documents. There is something very unusual about your pings, here are mine conducted just a few minutes ago, to those 2 IP addresses, then 7ticks Chicago, then Comcast Chicago:
Pretty impressed that you got those speeds without being located in the same data center (I presume)! Let me know the outcome of your investigation, I'd love to be corrected on this.
Like @Big Mike, I have the same "bad" latency to CQG Chi from my Chicago VPS (28ms), the latency to CQG Chicago based addresses is better from my VPS in New-Jersey (18ms)!
So this 64.208.51.192/26 IP range is not in Chicago, for sure, the .pdf might be wrong.
The IP for CQG New-York are good, below 1ms from NJ.
@redratsal
Fantastic idea. It takes 3 ms from Fermilab (Chicago) to "CQG Chicago" and back.
traceroute to 64.208.51.224 (64.208.51.224), 30 hops max, 40 byte packets
1 r-s-fcc2-server3-vlan110.fnal.gov (131.225.110.200) 0.602 ms 0.304 ms 0.267 ms
2 r-s-hub-fcc-vlan358.fnal.gov (131.225.15.129) 0.296 ms 0.289 ms 0.270 ms
3 r-s-edge-1-vlan608.fnal.gov (131.225.102.1) 0.422 ms 0.338 ms 0.317 ms
4 r-s-core-fcc-244.fnal.gov (131.225.15.246) 0.443 ms 0.360 ms 0.345 ms
5 r-edge-fcc2-1-132.fnal.gov (131.225.23.134) 0.526 ms 0.493 ms 0.466 ms
6 r-s-bdr-140.fnal.gov (131.225.23.141) 0.520 ms 0.447 ms 0.420 ms
7 fnal-mr2.fnal.gov (198.49.208.229) 0.393 ms 0.375 ms 0.326 ms
8 fnalmr3-ip-fnalmr2.es.net (134.55.41.41) 0.434 ms 0.377 ms 0.386 ms
9 chicsdn2-ip-fnalmr3.es.net (134.55.219.121) 1.811 ms 1.803 ms 1.785 ms
10 eqxchirt1-10g-chicsdn2.es.net (134.55.38.162) 1.975 ms 1.965 ms 1.974 ms
11 mpr1.ord7.us (206.223.119.86) 2.718 ms 2.401 ms 2.938 ms 12 xe-1-3-0.cr1.ord2.us.above.net (64.125.30.142) 2.982 ms 3.217 ms 3.001 ms
13 xe-0-0-0.cr2.ord2.us.above.net (64.125.28.234) 3.116 ms 38.500 ms 2.876 ms
14 xe-0-1-0.er2.ord2.us.above.net (64.125.25.110) 2.849 ms 2.715 ms 3.155 ms
(ORD is the designation for Chicago.)
It is about 28ms from Fermilab to University of Colorado Boulder. "CQG Chicago" is clearly very far away from Colorado.
traceroute to 128.138.140.44 (128.138.140.44), 30 hops max, 40 byte packets
1 r-s-fcc2-server3-vlan110.fnal.gov (131.225.110.200) 1.444 ms 0.685 ms 0.751 ms
2 r-s-hub-fcc-vlan358.fnal.gov (131.225.15.129) 0.663 ms 0.638 ms 0.613 ms
3 vlan303-r-d0-fcc2e-cas.fnal.gov (131.225.15.13) 0.905 ms 0.784 ms 0.764 ms
4 r-s-core-fcc-116.fnal.gov (131.225.23.117) 0.778 ms 0.767 ms 0.686 ms
5 r-edge-fcc2-1-132.fnal.gov (131.225.23.134) 0.882 ms 0.886 ms 0.851 ms
6 r-s-bdr-140.fnal.gov (131.225.23.141) 0.937 ms 6.321 ms 1.030 ms
7 fnal-mr2.fnal.gov (198.49.208.229) 0.799 ms 0.798 ms 0.772 ms
8 fnalmr3-ip-fnalmr2.es.net (134.55.41.41) 0.818 ms 0.832 ms 0.773 ms
9 chicsdn2-ip-fnalmr3.es.net (134.55.219.121) 2.234 ms 2.256 ms 2.236 ms
10 kanscr1-ip-chicsdn2.es.net (134.55.221.57) 12.781 ms 12.808 ms 12.822 ms
11 denvcr2-ip-kanscr1.es.net (134.55.209.45) 27.193 ms 25.972 ms 25.890 ms
12 esnet-l3-gw-1.frgp.net (198.129.248.126) 26.012 ms 25.970 ms 25.996 ms
13 frgp-re-ucb-b.colorado.edu (198.59.55.102) 87.218 ms 26.666 ms 26.255 ms
14 ucb-re-frgp-b.colorado.edu (198.59.55.101) 27.488 ms 27.721 ms 27.558 ms
15 hut-juniper.colorado.edu (128.138.81.249) 27.887 ms 27.861 ms 27.944 ms
16 engr-hut.colorado.edu (128.138.81.135) 27.932 ms 27.971 ms 27.922 ms
17 phys-engr.colorado.edu (128.138.81.35) 28.085 ms 28.145 ms 27.915 ms
Also, 19.7ms would be more in line with NJ to Chicago than NJ to Colorado. This is from my university in Cambridge, MA to Colorado (48ms!):
Executing exec(traceroute, -m 30 -q 3 -f 3, 128.138.140.44, 140)
traceroute to 128.138.140.44 (128.138.140.44), 30 hops max, 140 byte packets
3 128.103.0.142 (128.103.0.142) 0.446 ms 0.603 ms 0.356 ms
4 nox300gw1-vl-501-nox-harvard.nox.org (192.5.89.37) 0.758 ms 0.602 ms 0.559 ms
5 nox1sumgw1-vl-803-nox.nox.org (192.5.89.237) 0.628 ms 0.583 ms 0.575 ms
6 nox1sumgw1-peer-nox-internet2-192-5-89-18.nox.org (192.5.89.18) 22.721 ms 22.720 ms 22.715 ms
7 ae-0.10.rtr.kans.net.internet2.edu (64.57.28.36) 169.346 ms 182.247 ms 165.081 ms
8 i2-frgp-kans.net.internet2.edu (64.57.28.34) 46.412 ms 46.413 ms 46.419 ms
9 frgp-re-ucb-b.colorado.edu (198.59.55.102) 46.684 ms 46.673 ms 46.696 ms
10 ucb-re-frgp-b.colorado.edu (198.59.55.101) 47.988 ms 48.147 ms 47.938 ms
11 hut-juniper.colorado.edu (128.138.81.249) 48.278 ms 48.305 ms 48.861 ms
12 engr-hut.colorado.edu (128.138.81.135) 48.376 ms 48.320 ms 48.350 ms
13 phys-engr.colorado.edu (128.138.81.35) 48.458 ms 48.474 ms 48.409 ms
And again from Cambridge to Chicago (27ms!):
Executing exec(traceroute, -m 30 -q 3 -f 3, 64.208.51.224, 140)
traceroute to 64.208.51.224 (64.208.51.224), 30 hops max, 140 byte packets
3 128.103.0.142 (128.103.0.142) 0.586 ms 0.372 ms 0.340 ms
4 nox300gw1-vl-504-nox-harvard.nox.org (207.210.142.153) 0.560 ms 0.482 ms 0.470 ms
5 64.57.21.209 (64.57.21.209) 5.456 ms 5.437 ms 5.464 ms
6 above.net (198.32.118.25) 5.996 ms 6.017 ms 6.135 ms
7 xe-4-1-0.cr2.lga5.us.above.net (64.125.30.209) 6.248 ms 6.232 ms 6.350 ms
8 xe-0-2-0.cr2.ord2.us.above.net (64.125.27.33) 27.346 ms 27.389 ms 27.409 ms
9 xe-0-1-0.er2.ord2.us.above.net (64.125.25.110) 27.216 ms 27.266 ms 27.239 ms
@sam028 I suspect there is something about your VPS that is making a roundabout trip.