Welcome to NexusFi: the best trading community on the planet, with over 200,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 -- discounts are available after registering.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Ninja appears to be having chronic historical data issues lately. I have dodged most of these problems
because I start trading so early, but this morning all of Friday was missing from June contract / NQ. ... and
most every other instrument from what I have gathered.
Perhaps we could use this thread to discuss what is going on here.
I am using NT / AMP / CQG.
Is the continued historical data loss just with CQG or are other feeds affected.
Maybe someone can explain how the historical data is kept, who is keeping it... etc....
This is a killer for cats that depend on daily pivots and VP .
Someone fill a man in on how this thing works . ... @NinjaTrader ??
grazie
AJ
Nashville, Tennessee
"Life On The Edge of SR"
Can you help answer these questions from other members on NexusFi?
OK ... just received this from Kyle at NT support...
_________________________
Hello,
Thank you for contacting us to report the issue.
This is an issue which we are aware of and Historical Data Server maintenance is underway right now. It is likely that the missing data will be available again tomorrow morning based on the information which I see in our reporting system.
If other questions come up which I could assist with please let me know.
This is intended for the CEO of Ninja.
It has been weeks and weeks that there is missing historical data and once again today we have the same problem. This situation is totally unacceptable, and what is more annoying is the pathetic answers coming …