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)

"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'm satisfied with IQFeed. It's the most reliable and fastest quote feed I have ever used. Although I'm a resident in China, it's still very fast!" - Comment from Xiaofei

"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

"With HUGE volume on AAPL and RIMM for 2 days, everyone in a trading room was whining about freezes, crashes and lag with *******, RealTick, TS and Cyber. InvestorRT with IQFeed was rock solid. I mean SOLID!" - Comment from Public IRC Chat

"I'm very glad I switched to IQFeed. It's working perfectly with no lag, even during fast market conditions." - Comment from Andy via Email

"This beats the pants off CQG, I am definitely switching to the ProphetX 3.0!" - Comment from Stephen

"I've been using Neoticker RT with IQFeed for two months, and I'm very happy with both of the products (I've had IQFeed for two years with very few complaints). The service from both companies is exceptional." - Comment from Public Forum

"Very impressed with the quality of your feed - ******* is a real donkey in comparison." - Comment from A.C. via Email

"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.

"Interactive Brokers tick data was inconsistent, so I have switched to using DTN exclusively. It is great to no longer have to worry about my datafeed all day long." - Comment from Philippe

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