Hello GFIs1,

thank you for your information and the points to consider. The point to set IB's log to a time before trading is a good thing and better than my solution. I have set it to somewhere in the night where I don't trade but that creates a data gap.
I was not aware that these disconnects happen with other brokers too. Before I changed to IB I was with Tradestation ( pretty expensive ..). I never recognized disconnection problems with them, perhaps I'm a bit spoiled.
In regards to my trading style these IB connection errors are hard to handle for me. An example, in the moment when I want to open a position I watch for momentum, trade volume and speed. If they fit my defined requirements, I place my order most of the time 4 contracts. When the trade goes in my direction ( otherwise the stop takes me out of the trade) my NT set-up order management sells 2 contracts after 6 Ticks profit and another contract after 10 ticks profit while the stop loss of the forth contract is set to the point of entry the 4th contract I adjust either manually or it is sold through trade management after 20 ticks. When there is one of IB's connection errors the whole trade gets disarranged and absorbs my attention to "clean up IB's mess..." from my point of view of course.

Manfred
But if you confirm, that you see these disconnects at IB too I definitely have too look for another broker. I have heard good things about Global Futures and their CQG data connection. I will do some further research on them.

onehd1911 

Please excuse my English I'm from Germany and my English is very rusty. I have a connection issue using IB for day trading which affects the real time order execution with IB. You will probably only recognize it as a discrepancy in your personal order price tracking and the order price under which it is executed through IB. I created a support ticket at IB which is under work but no solution in sight. If it is not solved I will quit IB. My Environment: I use NinjaTrader's API to generate orders from NT DOM or chart trader in IB Trader Workstation. I have DTN IQFeed for the chart real time. I have strategies running for automated trading. The issue: I wondered that orders I placed in NT occasionally where not executed in IB or why the prices at which the order where executed at IB differ so much from the trade log in NT.. When I checked the log files in NT and IB I found periodically "connection loss and re-connect due to socket errors with the IB data gateway servers" entries in the IB TWS logfile. After help through the NT support and installation of the new TWS version through the NT support guys the issue could not been solved. I opened a ticket at IB 4 weeks ago. IB Support gave me a link to an non-public TWS version. The disconnection issues disappeared. So this is an software issue from IB. You will perhaps will not recognize it - it depends on the way you trade - because its symptom is an increases in the latency of the order execution time to 40 - 180 seconds. If the TWS Software detects that connection loss it tries to reconnect which most of the time is succesfult. But when you wonder why your profit is less than expected or your loss greater than expected check the TWS logfiles for those connection errors and you have the reason. Btw. this is not an internet connection issue (IB confirmed that). My IQFeed connection is stable and fast you cannot not wish to have a better connection. If somebody wants to have a copy of the conversation with the IB support or a copy of the TWS logiles I'm more than happy to send or publish it. Manfred

Thank you for the above information Manfred. A 40 to 180 second delay in executing an order would be devastating for me. Most of my trades don't last that long. I certainly feel for your situation. It sounds like you've been rather patient!

I have heard many good comments about IB's order fills, so I'm surprised to learn that they are experiencing a problem of this nature. I would think they would want to have this fixed 'yesterday'.

I wonder if anyone who is connecting to IB through Sierra Chart has experienced this problem?