I actually suspect they're making changes aimed at giving you that flexibility ... but somehow those changes screwed us up today. Actually given how it went wrong I suspect its a backup strategy so that they auto-switch you if the initial server farm fails . IB ... what's the story?
My log shows this as well: RU 22:51:51:892 JTS-Main: host = gw5.ibllc.com There was only one of those entries in my log, the other ones showed me connected to the Hong Kong server. Interestingly enough, I only got pinked out once (whereas you guys had multiple), and I only had one US server entry in my log.
i had no issues in the afternoon session. i didn't dare trade more than 2 contracts though- just in case. yeah, i'm curious to see if you're right. it did reconnect on the 1st try each time- something that usually is not the case. kiwi: i'm starting to get a better feel for the STW- i trade it a little before the HK opens. wish it had higher volume- though i have traded as many as 40 contracts without issue (in 10 contract increments, and, in all cases, i've been filled on them all). still would like to find an INSTITUTIONAL GRADE broker/platform offering all the asian markets...
Did anyone get an answer to what is going on with the log files? Curious to know if IB is finally fixing one of the major flaws in their system by using their other servers around the world as redundant backups in the event (quite frequently) that the local server farm goes down.
Happened to me as well, but I am on the US server. It went pink for like 15 to 30 sec. Luckily I was flat because my trade usually last minutes.
IB has investigated what happened. My log file showed a connection to the US BUT that was only because you logged in via the browser and not the standalone. The dialog that took place was only for a second or two and the connection for orders is still direct via the HK server. So something for us to know now ... if you log in browser based now you will host off the US but your connection will then go to HK (which shows further down the log file). The reason my final log showed HK was I was then using the standalone TWS. The CSR didn't know that (its probably part of the current developments) and after checking to confirm that I should be on the HK server thought something was messed up in the settings. Thus the request to reinstall. As for the pink out, they checked their logs, ISP data, etc and found no problems. They also confirmed with some local clients that they did not have any similar issues. So they believe that one of the pipes along the international internet route got congested giving some packet loss and a brief disconnection. I suspect an international gateway router might have had a problem ... but we don't have a system problem which was what worried me about it.
What kind of stupid explanations are those??? Pure fabrications!!! "So they believe that" a Chinese submarine was cutting the line... "I suspect an international" undersea lobster union member was sabotaging the cable.... Fu@k these morons plus crooks. I can tolerate crooks or morons, but I cannot stand both in the same person.