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)

"DTN feed was the only feed that consistently matched Bloomberg feed for BID/ASK data verification work these past years......DTN feed is a must for my supply & demand based trading using Cumulative Delta" - Comment from Public Forum Post

"There is no doubt that IQFeed is the best data provider. I am very satisfied with your services. And IQFeed is the only one that I would recommend to my friends. Now, most of them are using your product in China." - Comment from Zhezhe

"IQ feed works very well, does not have all of the normal interruptions I have grown used to on *******" - Comment from Mark

"Excellent datafeed !!!" - Comment from Arely

"If you are serious about your trading I would not rely on IB data for serious daytrading. Took me a while to justify the cost of IQ Feed and in the end, it's just a 2 point stop on ES. Better safe than sorry" - Comment from Public Forum

"After all the anxiety I had with my previous data provider it is a relief not to have to worry about data speed and integrity." - Comment from Eamonn

"I had always used ******* but for the past 2 weeks have been trying DTN IQFeed. Customer support has been extraordinary. They call just to make sure your problem hasn't recurred." - Comment from Public Forum

"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

"I cannot believe what a difference it makes trading with ProphetX!" - Comment from Bruce in Los Angeles

"Its working FABULOUSLY for me!! Holy cow...there has been so much I've been missing lately, and with this feed and Linnsoft software...I'm in the game now." - Comment from Chris R.

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 »Timestamp Issue

Author	Topic: Timestamp Issue (3 messages, Page 1 of 1)
SierraChart -Interested User- Posts: 25 Joined: May 23, 2006	Posted: Feb 27, 2008 06:44 PM Msg. 1 of 3 Any ideas what is causing the problem described here? http://supportboard.sierrachart.com/showthread.php?t=15234 Our best guess is that your timestamp message has the prior day's time value, but the next day's date around midnight when it is sent.
SierraChart -Interested User- Posts: 25 Joined: May 23, 2006	Posted: Feb 27, 2008 08:24 PM Msg. 2 of 3 I just realized that it may not be obvious as to my conclusion being that you don't understand how we do time stamp processing. being that the trade does not contain a date but only a time, we know that the date from the timestamp last received could be off by one day. We automatically make an adjustment for that. What I would like you to do make absolutely certain that when you transmit timestamp message that the date and time values are correct and correspond to each other.
DTN_Jay_Froscheiser -VP, Product Operations- Posts: 1746 Joined: May 3, 2004 DTN IQFeed/DTN.IQ/DTN NxCore	Posted: Feb 27, 2008 09:05 PM Msg. 3 of 3 Anthony, I think this issue is caused by a bug that has plagued us for the past few months. Unfortunately, it only happens periodically enough that we haven't been able to test our fixes effectively. We have new history server code in final QA testing and it appears this problem has been fixed in this new version (which is currently scheduled for release on 3/9). The problem occurs when we receive a tick exactly at midnight. Our servers are datestamping that tick to be the next day, while the time is the previous day. It was my understanding that the tick should have been corrected yesterday afternoon on our servers however. Thus, reloading the data should have corrected it if customers clear the stored data and reload. Again, the new servers should have this problem corrected (in addition to various enhancements such as more tick data and full exchange based tick correction). Jay Froscheiser DTN - Trading Markets