Every day (mostly at 5:00 est but at other times as well) my TWS losses its connection to the IB server for 10 or 20 seconds, which is a real problem for after hours traders like me. This happens each day, both at my office (T-1 connection) and at home (cable connection). A) why does this happen? B) is there anything I can do to keep this from happening? Many thanks.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
IB Suggestions & Improvements
- Thread starter Babak
- Start date
Quote from StLouisTrader:
Every day (mostly at 5:00 est but at other times as well) my TWS losses its connection to the IB server for 10 or 20 seconds, which is a real problem for after hours traders like me. This happens each day, both at my office (T-1 connection) and at home (cable connection). A) why does this happen? B) is there anything I can do to keep this from happening? Many thanks.
I have this problem too. I have tried sending IB a trouble ticket on this a few times but they reply that they think it is my internet connection. However, it always happens at 5pm EST and it happens on both of my internet connections (cable modem and DSL) which are from different providers.
Some server at IB is kicking people out automatically right after 5pm EST everyday, but I can't get anyone to believe me at IB. Now that another person has experienced this problem, I know it is not just me and I can be more aggressive in following up on the issue.
The identity token for secure transactions is a really good idea and done very well with one exception.
It would be very nice to be able to associate one identity token with several accounts rather than having to get a separate one for each account. I'm facing having to get 6 of them for my F/F accounts...
Perhaps there are technical limitations with the devices? A device with a hidden private key and an associated public key would be able to do this by registering the appropriate public key with each relevant account.
Thanks for creating such a great service!
It would be very nice to be able to associate one identity token with several accounts rather than having to get a separate one for each account. I'm facing having to get 6 of them for my F/F accounts...
Perhaps there are technical limitations with the devices? A device with a hidden private key and an associated public key would be able to do this by registering the appropriate public key with each relevant account.
Thanks for creating such a great service!
The IB people have been super at responding on this site.
Currently, IB order servers only permit conditions to trigger LIMIT or MKT orders.
Please allow TRAIL orders to have conditions.
One response is "just use the API". The problem with using the API is that if you become disconnected from the IB servers or experience latency because of a network issue, then you are out of luck. It also means that you have to up the ante to having a machine always connected.
Is there a regulatory reason why this can't be done?
Thanks!
Currently, IB order servers only permit conditions to trigger LIMIT or MKT orders.
Please allow TRAIL orders to have conditions.
One response is "just use the API". The problem with using the API is that if you become disconnected from the IB servers or experience latency because of a network issue, then you are out of luck. It also means that you have to up the ante to having a machine always connected.
Is there a regulatory reason why this can't be done?
Thanks!
Quote from kej:
The identity token for secure transactions is a really good idea and done very well with one exception.
It would be very nice to be able to associate one identity token with several accounts rather than having to get a separate one for each account. I'm facing having to get 6 of them for my F/F accounts...
Perhaps there are technical limitations with the devices? A device with a hidden private key and an associated public key would be able to do this by registering the appropriate public key with each relevant account.
Thanks for creating such a great service!
In its current implementation, the token is associated 1:1 with a single account. It is not trivial to make it 1:many. It probably can be done but this is a guess, as I am not 100% sure of the software/hardware restrictions (the hardware is 3rd party). But I agree it is annoying, or more, to have multiple security devices. I will look into it.
Quote from alanm:
I get disconnected at 17:00 ET in at least one of my accounts, too. I've had an open ticket on it for a while, to which I've added a link to this thread. Hopefully, they'll see the pattern.
We are working on this. We got enough reports about disconnects at 16:00 and 17:00 EST that it seems likely there is some systematic problem. It isn't so easy to track this down.
Dear IB,
This is the 3rd time I've asked you to respond to a question I had from about 3 or 4 pages back. Could you please reply?
Thanks
This is the 3rd time I've asked you to respond to a question I had from about 3 or 4 pages back. Could you please reply?
Thanks
Quote from IBj:
We are working on this. We got enough reports about disconnects at 16:00 and 17:00 EST that it seems likely there is some systematic problem. It isn't so easy to track this down.
If there is anyway I can help and provide specific information on my end, I would be more than willing to help.
Many thanks for checking.Quote from IBj:
In its current implementation, the token is associated 1:1 with a single account.
...
By the way, it is worth noting that if I have an identity token as an advisor but all of the money is in managed accounts, then there isn't really token-based protection for the money unless BOTH the advisor and the managed account have a security token.