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)
A big "Thanks" to Ray and his staff. I spoke with Ninja a day or so ago and they were very forthcoming about the CQG issue mentioned here....and I am confident they will deliver as good a solution as is possible.
As mentioned by others already....I would rather have Ninja take the time and test instead of rushing it into production.
I think the issues identified in this post suggest to me, that its a good idea to invest in a decent connection/hosting. Or I may look a secondary market data feed. I think many more people are going down this route after connectivity issues with many vendors over recent times, however this of course is no guarantee but we can only be prudent.
In this case a decent connection helps, but is not enough.
Normal and good behavior:
Tuesday, February 18, 2014 2:48:07 AM
Tracing route to 208.48.16.224 over a maximum of 30 hops
1 2 ms <1 ms <1 ms [TOP SECRET !!!]
2 23 ms <1 ms <1 ms [TOP SECRET !!!]
3 <1 ms <1 ms <1 ms [TOP SECRET !!!]
4 <1 ms <1 ms <1 ms chp-brdr-04.inet.qwest.net [63.146.26.229]
5 <1 ms <1 ms <1 ms cer-cntr-01.inet.qwest.net [205.171.93.54]
6 1 ms 1 ms 1 ms 67.128.209.11
7 1 ms <1 ms <1 ms 208.48.16.224
Trace complete.
Ugly route :
Wednesday, February 19, 2014 11:03:31 PM
Tracing route to 208.48.16.224 over a maximum of 30 hops
1 1 ms <1 ms <1 ms [TOP SECRET !!!]
2 <1 ms <1 ms <1 ms [TOP SECRET !!!]
3 <1 ms <1 ms <1 ms [TOP SECRET !!!]
4 21 ms <1 ms <1 ms chp-brdr-04.inet.qwest.net [63.146.26.229] 5 361 ms * * cer-cntr-01.inet.qwest.net [205.171.93.54]
6 339 ms * * 67.128.209.11
7 * 377 ms * 208.48.16.224
8 * * * Request timed out.
9 377 ms 376 ms 373 ms 208.48.16.224
Trace complete.
Nice illustration of the issue. A prudent DR plan helps but there's no guarantees. Hopefully the fix comes to market cleanly. What's the max downtime you've seen when it drops?
Not good mate I'm looking to use these guys, is there an official SLA (service level agreement) on outages?.
I think they advertise they've data centres routing users globally, are there any views on particular regions that are suffering or is it a global issue with the vendor?
Anyone have a clue why it takes a couple of days to get hooked up to Continuum through Mirus? Never had that problem before with any other datafeed - usually turns on immediately. I use TradeStation and Ninja with Mirus. Thanks.
Does "slow connection state" mean delayed (latency?) or filtered data?
What amount of delay and/or data bandwidth are ranked as "slow" by the API?
And what about primary connection issues?
If NT will not report lost connection, will the user know about delayed/filtered connection state?
I have had disconnections since end of January almost every day. Mostly disconnected price feed with price data is coming, once with delayed (by several minutes) time stamp... I had several disconnections of the primary connection too.
