DTN IQFeed, DTN.IQ, DTN ProphetX Support Forums

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)

"For anyone considering using DTN.IQ for a data feed, my experience with the quality of data and the tech support has been very positive." - Comment from Public Forum

"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

"Version 4.0.0.2 has been working well for me and I appreciate that it is now a much tighter client to work with. I feel I can go to press with my own application and rely on a stable platform" - Comment from David in IA.

"I ran your IQFeed DDE vs. my broker vs. a level II window for some slow-moving options. I would see the level II quote change, then your feed update instantaneously. My broker's DDE, however, would take as much as 30 seconds to update. I am not chasing milliseconds, but half a minute is unacceptable." - Comment from Rob

"Excellent datafeed !!!" - Comment from Arely

"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

"Previously I was using *******. IQFeed is WAY more economical, and for my charting needs is just as good, if not better." - Comment from Public Forum Post

"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

"If someone needs the best quality data and backfill beyond what their broker provides at a rate that is the best in the industry, I highly recommend IQFeed." - Comment from Josh via Public Forum

"Everything is working great with the API. I love it." - Comment from Calvin

Home

Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather

DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter

»Forums Index »Archive (2017 and earlier) »Data and Content Support »HIT timing off

Author	Topic: HIT timing off (3 messages, Page 1 of 1)
adrian -Interested User- Posts: 28 Joined: Oct 24, 2008	Posted: Jan 17, 2010 04:03 PM Msg. 1 of 3 I'm trying to get a set of 1min bars back starting at 9:30 EST and going for the next 20 minutes. I connect from Java using the TCP/IP and send: HIT,SKF,60,20100115 093000,20100115 095000,21,093000,160000,1,HIT_1,5 As I understand it, this should give data for 'SKF' in 1min (60 sec) bars, for Friday Jan 15th 2010 from 9:30am-9:50am. It will give a max of 21 bars and filters out after hours data. What I get is: HIT_1,2010-01-15 17:03:00,22.7000,22.7000,22.7000,22.7000,11787379,150, HIT_1,2010-01-15 17:05:00,22.6900,22.6900,22.6900,22.6900,11791379,4000, HIT_1,2010-01-15 17:28:00,22.7000,22.7000,22.7000,22.7000,11791879,500, HIT_1,2010-01-15 17:30:00,22.7200,22.7200,22.7200,22.7200,11791979,100, ... So it's not starting when I requested and it's giving after hours data which I said should be filtered. I tried this with similar dates on a number of other stocks and they all behaved similarly. Ideas for what I can do to fix this?
adrian -Interested User- Posts: 28 Joined: Oct 24, 2008	Posted: Jan 18, 2010 10:12 AM Msg. 2 of 3 I think I got diverted into the wrong forums, not sure how that happened. Sorry about that. And when I ran the program this morning it worked as expected. I don't know if there was some glitch over the weekend or what happened but everything's good now.
DTN_Steve_S -DTN Guru- Posts: 2093 Joined: Nov 21, 2005	Posted: Jan 19, 2010 02:12 PM Msg. 3 of 3 Hello adrian, sorry for the delay in responding. I'm glad it seems to be working for you once again. Just to verify, there was an issue with one of our server farms over the weekend that would explain the problems you saw.