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)

"Excellent datafeed !!!" - Comment from Arely
"IQFeed version 4 is a real screamer compared to anything else I have seen." - Comment from Tom
"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've never had DTN go out on me since switching. ******* would go down a couple times every month when I was using them." - Comment from Bryce in AL.
"You have an excellent feed. Very few spikes for Spot Forex." - Comment from Public Forum Post
"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
"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
"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
"I "bracket trade" all major news releases and I have not found one lag or glitch with DTN.IQ feed. I am very comfortable with their feed under all typical news conditions (Fed releases, employment numbers, etc)." - Comment from Public Forum
"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.
Home  Search  Register  Login  Blogs Recent Posts

Information on DTN's Industries:
DTN Oil & Gas | DTN Trading | DTN Agriculture | DTN Weather
Follow DTN_IQFeed on Twitter
DTN.IQ/IQFeed on Twitter
DTN News and Analysis on Twitter
Viewing User Profile for: DTN_Steve_S
About Contact
Joined: Nov 21, 2005 02:10 PM
Last Post: Jan 18, 2019 01:56 PM
Last Visit: Jan 18, 2019 02:25 PM
Yahoo IM:
Post Statistics
DTN_Steve_S has contributed to 2064 posts out of 18877 total posts (10.93%) in 4,811 days (0.43 posts per day).

20 Most recent posts:

NOTE: this build will correctly display prices in streaming quote/trades (Level 1 / SnapQuote). However, the history servers still need updated before you will see correct prices there (Time&Sales/Charts). That release is coming soon on the server side and this build will support it when they roll out.

This release also has several bug fixes as follows:

IQFeed v6.0.1.0 - 2019/01/18 - Changes since last Release
• Added support for 64bit (8+ decimals) precision prices in streaming (Level 1) data and History data (as soon as the history servers support rolls out).
• Time & Sales now autosizes on headers and data.
• Time & Sales filters button now stays active while filters are enabled.
• SnapQuote now has the ability to change fonts and autosizes the grid appropriately so it can be read at higher resoultions and scaling.
• Watchlist right-click menu cleaned up.
• Watchlist alerts reset screen will now accept all appropriate keystrokes.
• Fixed several settings with the lower studies settings either not working or not saving in charts.
• News now saves splitter window sizes and should load up in a more user friendly state.

You can download this build on the IQFeed website here:§ion=download

If you encounter issues with this build (especially anything with the specific fixes mentioned above), please make sure to contact our Customer Support group so that the issues can get logged/addressed as necessary.
Edited by DTN_Steve_S on Jan 18, 2019 at 02:25 PM

IQFeed Developer Support » Trade Aggressor Side Jan 18, 2019 07:21 AM (Total replies: 3)

This will be in IQFeed 6.1.

Data and Content Support » Strange historical data coming from IQFeed Dec 20, 2018 02:30 PM (Total replies: 1)

Sorry for the delay responding here. These have been corrected.

Data and Content Support » Wrong London Exchange data Dec 20, 2018 02:17 PM (Total replies: 1)

Hello, we are looking into this.

IQFeed Developer Support » Get underlying for a futures option Dec 14, 2018 02:04 PM (Total replies: 3)

OK, I understand now. You're talking about serial options. We do not have this data directly in the feed currently. However, the next version of IQFeed (6.1) will have a way you can figure it out indirectly.

We are adding a List of contract months to the futures symbol's fundamental data.

As a result, using @C as an example:

@CF19C3300 is a serial option.

In IQFeed 6.1, watching @C# will give you a list of contract months so you will be able to compare the option Month code (F) to the list of future contract months (MKNUZ) and be able to determine what the next one would be which the serial month would apply to.

IQFeed Developer Support » Get underlying for a futures option Dec 14, 2018 11:58 AM (Total replies: 3)

Hello, sorry for the delay responding here.

I'm not sure I understand what you're asking for.

Future Options are issued based on a specific futures contract and expire at the same time (or close to).

The symbology also has the underlying contract specified as well.

For example


is an option for @ESZ18

IQFeed Developer Support » About L1 level Connection Dec 5, 2018 07:55 AM (Total replies: 5)

Have you updated your software to use the current protocol?

The 99:99:99 timestamps (and dates) were a way of signaling invalid values in older protocols.

I can't verify at the moment since it's currently trading but those fields should be blank rather than filled with 9s in the current protocols when they aren't valid.

IQFeed Developer Support » About L1 level Connection Nov 30, 2018 05:38 AM (Total replies: 5)

Can you post the raw IQFeed output messages you get that show the incorrect dates?

IQFeed Developer Support » About L1 level Connection Nov 29, 2018 06:10 AM (Total replies: 5)

Hello, I believe I also replied to some of this via email but I'll answer here as well for future readers.

1. I don't know of anything that should cause this described behavior. Please give me some examples of the exact request/responses you are getting from the feed in both scenarios.
2. This looks like you aren't specifying a protocol for the connection to use. For backwards compatibility reasons, the feed defaults new connections to the oldest supported protocol (4.9) which did not include subsecond timestamps.
3. We only store bid/ask prices (no sizes) information in historical data.

IQFeed Developer Support » Message Content Flags Nov 20, 2018 05:22 AM (Total replies: 7)

The data in the fields themselves is still correct. It's only the Message Contents field that is misleading.

As a result, the solution/work around to this issue would be to ignore the message contents field on summary messages and check the fields manually (again, this is only necessary for summary messages).

IQFeed Developer Support » Message Content Flags Nov 19, 2018 02:31 PM (Total replies: 7)

No, nothing changed on our side.

One possible explanation is if you were watching these symbols on another connection to the feed during the previous test and not during the current test.

The Message Contents field is populated based on the last message received from the servers.

In the scenario where one connection is already watching the symbol, and a 2nd client connects and watches the same symbol, the summary message is generated locally on your machine (cause it already has all the data there). However, the Message contents on the summary message for the 2nd client is not re-generated and instead will contain whatever the values that apply to the most recent message received from the server for that symbol (so in your example, it was a bid/ask update).

IQFeed Developer Support » Message Content Flags Nov 19, 2018 12:39 PM (Total replies: 7)

Slight correction here. The existence of the field flag in the Message Contents field does not necessarily indicate a change in value, simply that it was updated (sometimes with the same value).

In your scenario (initial snapshot summary message after having just sent a watch request), I would also expect the open flag to be set if the message had an open value populated.

If you watch pre-market open when the open field is still blank, the 'o' should populate in the trade message in which the open field populates.

Can you send me an example of this not happening (I just checked a few symbols and they all have had the 'o' in the Message Contents field)?

IQFeed Developer Support » Timezone of timestamps Nov 19, 2018 05:32 AM (Total replies: 1)

Hello Yair, our servers do observe DST. As a result,

EST/EDT depending on daylight summer time in New York

is the correct answer to question number 1. As a result, the answer to number 2 should also be:

That we are mistaken and the data content matches the reported time in New York.

Let me know what is causing the confusion for you and I'm happy to offer advice to clear that up.

Thanks for the logfile Matt.

This is a restriction of trial accounts (only 4 days of tick history and 1 year of daily data). As a result, your requests are getting converted to only request 365 days instead of 5000 behind the scenes.

I'm not able to duplicate this and, off the top of my head, I can't think of any scenario where you would be seeing this behavior.

Can you email me (to dev support) an IQFeed logfile with All Logging enabled? You can configure/enable logging in IQFeed using the Diagnostics app. Note that after running your test and saving the logfile, you will want to reduce the logging back to default levels for performance reasons.

IQFeed Developer Support » History LookupError Nov 13, 2018 11:02 AM (Total replies: 2)

Socket error 10060 is a timeout error on the connection from your machine to our servers.

Each request you make to the feed is handled in it's own connection to the server (Create -> Connect -> Request -> Receive -> Close).

As a result, if you're spinning through 3000 stocks, that is 3000 different socket connections to the server over the course of however long it takes you to make those requests.

We have investigated these sorts of reports a few different times over the years and we've never been able to replicate this reliably or identify a specific cause (all of our tests from both internal and external to our network have not been able to replicate).

If it's something that just recently started, you might try resetting your router/modem (most non-enterprise class hardware will occasionally hiccup under heavy connection load). Of course we are happy to help troubleshoot this with you but most of the time, since a simple re-request usually succeeds, most developers choose to simply implement that (as you have) and not worry about it anymore unless the problem gets worse.

IQFeed Developer Support » Invalid Open in L1 summary message Nov 13, 2018 06:46 AM (Total replies: 4)

OK, I'm pretty sure I've figured out what is going on here.

We have a maintenance process that runs right around that time in the early AM that clears the previous day's OHL values. My guess is that you caught it in the middle of that process running which is why only some of the symbols were affected.

If you startup sometime after 4AM eastern, you should be safe.

IQFeed Developer Support » Consuming IQFeed APIs via C++ on Linux Nov 12, 2018 06:49 AM (Total replies: 16)

This sounds like the intended behavior of the feed. The client app on your machine is designed to disconnect and shut down if it isn't in use and it does an ICMP ping to the servers as part of it's shutdown process. As a result, the ICMP failure error message isn't the cause of the shutdown.

If you want to keep the app running, you have to maintain a connection to it.

IQFeed Developer Support » Invalid Open in L1 summary message Nov 12, 2018 06:45 AM (Total replies: 4)

Hello, sorry for the delay responding here.

I'm not seeing this same behavior currently (~6:45AM Eastern). Can you provide some specific examples of this?

IQFeed Developer Support » avoiding settlement "ticks" for futures Nov 1, 2018 08:54 AM (Total replies: 3)

In your example, All three sets of fields (Last, Extended Trade, and Most Recent Trade) will reflect the last trade price of 2500.00.

We have separate fields (Settle and Settlement Date) to display the settle information in streaming data. The settlement price is copied to the Close field but never the trade fields.

Message Contents on a summary message isn't very useful since summary messages populate all fields and the purpose of Message Contents is to tell you what was populated in the message.
Edited by DTN_Steve_S on Nov 1, 2018 at 08:55 AM

Time: Tue January 22, 2019 9:17 AM CFBB v1.2.0 15 ms.
© AderSoftware 2002-2003