@kronie agree with you. But this latency issue has to do with hops right before the CQG server. You can see where it happens most of the time on the tracert. I have actually seen it hit 800ms which is kind of ridiculous. Whose fault it is who knows? But even the guys running the data center at Steadfast in Chicago are saying they have seen many problems with routes the last few months. So there is something going on with the backbone so to speak.
"The day I became a winning trader was the day it became boring. Daily losses no longer bother me and daily wins no longer excited me. Took years of pain and busting a few accounts before finally got my mind right. I survived the darkness within and now just chillax and let my black box do the work."
The following 2 users say Thank You to liquidcci for this post:
Platform: "I trade, therefore, I AM!"; Theme Song: "Atomic Dog!"
Favorite Futures: EMD, 6J, ZB
Posts: 798 since Oct 2009
Thanks: 216 given,
since it has been isolated to the "in-between" zone, one has to look at the servers used to handle routing on the backbone. Cicso's architecture is preferred to others, but there are other machines used. They are in doubt and are failing. On the backbone and on the back plane (the integrated circuit board) that the HDD's are attached to the physical server / router box, are using simplistic chips and chipsets that are failing over. At this point, they're executing their "distress" steps, and hence the massive throttling or 800ms ping counts.
simply put, those boxes need replacement, as they are just before the point of melting down from excessive wear and tear. imagine that, with no moving parts, they're melting down from wear and tear.
The following 2 users say Thank You to kronie for this post:
I upgraded to ninja v22 and have the CQG feed. Ever since upgrading I've noticed more disconnects but also now when I have a disconnect ninjatrader crashes completely and I need to restart. I never had this problem before. I'm wondering, is anyone else experiencing this? thanks
The following user says Thank You to Sk8ter for this post:
I have not seen any differences regarding the disconnection issue, but the upgrade to 22 broke some custom indicators, had to manually re add references to dll files in NT. I am using v22 since the weekend. tested from different locations so connectivity issue on my side ruled out.