NexusFi: Find Your Edge


Home Menu

 





Leased Server anybody every do this?


Discussion in Brokers

Updated
      Top Posters
    1. looks_one artemiso with 6 posts (3 thanks)
    2. looks_two Big Mike with 3 posts (1 thanks)
    3. looks_3 c12345 with 2 posts (0 thanks)
    4. looks_4 sam028 with 2 posts (4 thanks)
      Best Posters
    1. looks_one sam028 with 2 thanks per post
    2. looks_two redratsal with 1 thanks per post
    3. looks_3 artemiso with 0.5 thanks per post
    4. looks_4 Big Mike with 0.3 thanks per post
    1. trending_up 9,278 views
    2. thumb_up 12 thanks given
    3. group 9 followers
    1. forum 17 posts
    2. attach_file 4 attachments




 
Search this Thread

Leased Server anybody every do this?

  #11 (permalink)
 artemiso 
New York, NY
 
Experience: Beginner
Platform: Vanguard 401k
Broker: Yahoo Finance
Trading: Mutual funds
Posts: 1,152 since Jul 2012
Thanks Given: 784
Thanks Received: 2,685


Big Mike View Post
Those are not in Chicago. Looks like Colorado.

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.)

Reply With Quote

Can you help answer these questions
from other members on NexusFi?
Better Renko Gaps
The Elite Circle
My NT8 Volume Profile Split by Asian/Euro/Open
NinjaTrader
The space time continuum and the dynamics of a financial …
Emini and Emicro Index
ZombieSqueeze
Platforms and Indicators
New Micros: Ultra 10-Year & Ultra T-Bond -- Live Now
Treasury Notes and Bonds
 
Best Threads (Most Thanked)
in the last 7 days on NexusFi
Get funded firms 2023/2024 - Any recommendations or word …
59 thanks
Funded Trader platforms
37 thanks
NexusFi site changelog and issues/problem reporting
24 thanks
GFIs1 1 DAX trade per day journal
22 thanks
The Program
19 thanks
  #12 (permalink)
 
Big Mike's Avatar
 Big Mike 
Manta, Ecuador
Site Administrator
Developer
Swing Trader
 
Experience: Advanced
Platform: Custom solution
Broker: IBKR
Trading: Stocks & Futures
Frequency: Every few days
Duration: Weeks
Posts: 50,399 since Jun 2009
Thanks Given: 33,175
Thanks Received: 101,539


artemiso View Post
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.)

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.

Free Product Demo, Tools and Sample Databases | IP2Location.com

Mike

We're here to help: just ask the community or contact our Help Desk

Quick Links: Change your Username or Register as a Vendor
Searching for trading reviews? Review this list
Lifetime Elite Membership: Sign-up for only $149 USD
Exclusive money saving offers from our Site Sponsors: Browse Offers
Report problems with the site: Using the NexusFi changelog thread
Follow me on Twitter Visit my NexusFi Trade Journal Reply With Quote
  #13 (permalink)
 artemiso 
New York, NY
 
Experience: Beginner
Platform: Vanguard 401k
Broker: Yahoo Finance
Trading: Mutual funds
Posts: 1,152 since Jul 2012
Thanks Given: 784
Thanks Received: 2,685


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:


Reply With Quote
  #14 (permalink)
 
Big Mike's Avatar
 Big Mike 
Manta, Ecuador
Site Administrator
Developer
Swing Trader
 
Experience: Advanced
Platform: Custom solution
Broker: IBKR
Trading: Stocks & Futures
Frequency: Every few days
Duration: Weeks
Posts: 50,399 since Jun 2009
Thanks Given: 33,175
Thanks Received: 101,539

I will have to look later. The Zen Fire pings from same server are <1ms


# ping 68.87.72.134
PING 68.87.72.134 (68.87.72.134) 56(84) bytes of data.
64 bytes from 68.87.72.134: icmp_req=1 ttl=53 time=0.986 ms
64 bytes from 68.87.72.134: icmp_req=2 ttl=53 time=0.934 ms
64 bytes from 68.87.72.134: icmp_req=3 ttl=53 time=0.985 ms
64 bytes from 68.87.72.134: icmp_req=4 ttl=53 time=0.906 ms
64 bytes from 68.87.72.134: icmp_req=5 ttl=53 time=1.18 ms
64 bytes from 68.87.72.134: icmp_req=6 ttl=53 time=0.982 ms
64 bytes from 68.87.72.134: icmp_req=7 ttl=53 time=1.00 ms
^C
--- 68.87.72.134 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6004ms
rtt min/avg/max/mdev = 0.906/0.998/1.189/0.087 ms

Mike

We're here to help: just ask the community or contact our Help Desk

Quick Links: Change your Username or Register as a Vendor
Searching for trading reviews? Review this list
Lifetime Elite Membership: Sign-up for only $149 USD
Exclusive money saving offers from our Site Sponsors: Browse Offers
Report problems with the site: Using the NexusFi changelog thread
Follow me on Twitter Visit my NexusFi Trade Journal Reply With Quote
Thanked by:
  #15 (permalink)
 artemiso 
New York, NY
 
Experience: Beginner
Platform: Vanguard 401k
Broker: Yahoo Finance
Trading: Mutual funds
Posts: 1,152 since Jul 2012
Thanks Given: 784
Thanks Received: 2,685


Big Mike View Post
I will have to look later. The Zen Fire pings from same server are <1ms


# ping 68.87.72.134
PING 68.87.72.134 (68.87.72.134) 56(84) bytes of data.
64 bytes from 68.87.72.134: icmp_req=1 ttl=53 time=0.986 ms
64 bytes from 68.87.72.134: icmp_req=2 ttl=53 time=0.934 ms
64 bytes from 68.87.72.134: icmp_req=3 ttl=53 time=0.985 ms
64 bytes from 68.87.72.134: icmp_req=4 ttl=53 time=0.906 ms
64 bytes from 68.87.72.134: icmp_req=5 ttl=53 time=1.18 ms
64 bytes from 68.87.72.134: icmp_req=6 ttl=53 time=0.982 ms
64 bytes from 68.87.72.134: icmp_req=7 ttl=53 time=1.00 ms
^C
--- 68.87.72.134 ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6004ms
rtt min/avg/max/mdev = 0.906/0.998/1.189/0.087 ms

Mike

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.

Reply With Quote
  #16 (permalink)
 
sam028's Avatar
 sam028 
Site Moderator
 
Posts: 3,765 since Jun 2009
Thanks Given: 3,825
Thanks Received: 4,629


artemiso View Post
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.

It's the same building, and the same data center.

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.

From NJ VPS to CQG Chicago:


From NJ VPS to CQG New-York ():


From Chicago VPS to CQG Chicago ():

Success requires no deodorant! (Sun Tzu)
Follow me on Twitter Reply With Quote
Thanked by:
  #17 (permalink)
 
redratsal's Avatar
 redratsal 
Milan (I)
 
Experience: Advanced
Platform: Ninjatrader
Broker: Kinetick
Trading: FDAX,6E,CL,YM,NQ,ES
Posts: 1,648 since Oct 2010
Thanks Given: 1,215
Thanks Received: 2,090

trace routed 68.87.72.134 and 64.208.51.224


Visit my NexusFi Trade Journal Reply With Quote
  #18 (permalink)
 artemiso 
New York, NY
 
Experience: Beginner
Platform: Vanguard 401k
Broker: Yahoo Finance
Trading: Mutual funds
Posts: 1,152 since Jul 2012
Thanks Given: 784
Thanks Received: 2,685

@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.

Reply With Quote




Last Updated on July 19, 2012


© 2024 NexusFi™, s.a., All Rights Reserved.
Av Ricardo J. Alfaro, Century Tower, Panama City, Panama, Ph: +507 833-9432 (Panama and Intl), +1 888-312-3001 (USA and Canada)
All information is for educational use only and is not investment advice. There is a substantial risk of loss in trading commodity futures, stocks, options and foreign exchange products. Past performance is not indicative of future results.
About Us - Contact Us - Site Rules, Acceptable Use, and Terms and Conditions - Privacy Policy - Downloads - Top
no new posts