|
Join the 80,000 other DTN customers who enjoy the fastest, most reliable data available. There is no better value than DTN!
(Move your cursor to this area to pause scrolling)
"I am enjoying the feed very much - so superior to the broker provided feed I was previously using." - Comment from George
"DTN has never given me problems. It is incredibly stable. In fact I've occasionally lost the data feed from Interactive Brokers, but still been able to trade because I'm getting good data from DTN." - Comment from Leighton
"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark
"I just wanted to let u know that your data feed/service is by far the best!!! Your unfiltered tick data is excellent for reading order flow and none of your competitors delivers this quality of data!" - Comment from Peter via Email
"I was on the phone with a friend who uses CQG and right after the Fed announcement, CQG was as much as 30 seconds behind DTN.IQ. Some quotes were off by as much as 15-18 cents. Your feed never missed a beat." - Comment from Roger
"I just wanted to say how happy I am with your service. I was able to download the API docs last week and I was able to replicate Interactive Brokers historical bar queries and realtime bar queries over the weekend. That was about one of the fastest integrations that I've ever done and it works perfectly!!!!" - Comment from Jason via Email
"I used to have *******, but they are way more money for the same thing. I have had no probs with data from DTN since switching over." - Comment from Public Forum Post
"Thanks for the great product and support. During this week of high volume trading, my QuoteTracker + IQ Feed setup never missed a beat. Also, thanks for your swiftness in responding to data issues. I was on ******* for a few years before I made the switch over early this year, and wish I had done it a long time ago." - Comment from Ken
"I would just like to say that IQFeed version 4 is running very well and I am very happy with its performance. I would also like to extend a big thanks for the fast and efficient help that I always receive. My questions and concerns are always addressed promptly. Way to go!" - Comment from Josh in CO.
"Can I get another account from you? I am tired of ******* going down so often" - Comment from George
|
|
|
|
Joined: |
May 12, 2021 06:14 AM |
Last Post: |
May 12, 2021 05:25 PM |
Last Visit: |
May 12, 2021 05:25 PM |
Website: |
|
Location: |
|
Occupation: |
|
Interests: |
|
|
|
ryporter has contributed to 4 posts out of 21194 total posts
(0.02%) in 1,101 days (0.00 posts per day).
20 Most recent posts:
I should also note that I'm on version 5.0 of the API. I know that's an old version.
No need to dig into this if no one else is seeing any issues. It may be an issue on my end anyway, and I've found a workaround that patches together data collected before and after April 12, instead of collecting the last couple months all at once.
It's been a while since I've worked on this software, but I believe that it is sending the following request.
HTD,CNGT,50,,,,1,321687954
For this request, I'm not seeing any ticks after April 12. However, if I change the third column from 50 to 20, so that April 12 is not covered, then I see ticks after that date.
It's very possible that there's something else in my software that's getting tripped up by the error lines that I'm trying to ignore.
I ran my software again, this time requesting data starting from a date after April 12. This resulted in many more ticks being returned. It's still aggregate data, but the results look to be in line with what I was seeing before the backfill.
In summary, I seem to be retrieving fewer ticks for days after April 12, but only if I ask for data starting from before April 12.
So, I'm wondering if whatever is causing those "Connection Timeout Error" lines to appear in the results is also affecting the data that is returned for a stock after that point.
Since the backfill was completed, historical data requests done via the API receive lines like with:
"E,Connection Timeout Error."
Since these occur after receiving data around the time of the outage, I assume I should just ignore them.
More importantly, I'm also seeing far fewer ticks on the trading days starting after April 12. I only have aggregate data right now, but I'm seeing about 1/30 as many ticks on each day.
These are all OTCBB stocks.
|
|