2000ms is a long time in HSI. I have had to adapt the way I trade to factor in latency from Thailand to HK (actually 200-300ms despite short distance).
what is the IP address of IB Hong Kong server ? I tried to ping from shanghai, china through FTTB, ADSL, ISDN to gw1.ibllc.com ( US server ?) , the result is always above 2500ms or simply shows "request times out". I want to try to pin the IB Hong Kong Server, becauze I use this server to trade HSI, but recently many breaks from the server during the trading time. I had to use another broker to hedge my positions. The problem is that that another broker ( a Hong KOng broker) sent me a letter this week saying that they are going to adopt the IB TWS for their trading from August, so I am desperately trying to fix the network problem or find a third HSI broker. Anyway, can someone kindly advise the ping address of IB hong kong server ?
202.1.7.3:4000 TWS disconnects on packet loss so steady ping or loss of ability to ping does not necessarily correlate with TWS disconnects which are triggered by packet loss. I am in Thailand and have similar issues with disconnects recently. I am uncertain as to whether this is a TWS issue or an ISP routing issue. I have had to effectively stop trading.
I use the same IB HK server (from an Australian location) and have had no problems with connection to IB over the last year except for a local flood which took out the cable headend and one major power failure at the IB node. All else has been fine. IB has been fine and the ping time has been around 170ms to 175ms from here.
I try to pin IB HK server, following three results ============================================== FIRST PIN C:\Documents and Settings\user>ping gw1.ibllc.com.hk Pinging gw1.ibllc.com.hk [202.1.7.3] with 32 bytes of data: Request timed out. Reply from 202.1.7.3: bytes=32 time=1249ms TTL=44 Reply from 202.1.7.3: bytes=32 time=1392ms TTL=44 Reply from 202.1.7.3: bytes=32 time=1539ms TTL=44 Ping statistics for 202.1.7.3: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 1249ms, Maximum = 1539ms, Average = 1393ms ============================================== SECOND PIN C:\Documents and Settings\user>ping gw1.ibllc.com.hk Pinging gw1.ibllc.com.hk [202.1.7.3] with 32 bytes of data: Reply from 202.1.7.3: bytes=32 time=1331ms TTL=44 Request timed out. Request timed out. Reply from 202.1.7.3: bytes=32 time=1973ms TTL=44 Ping statistics for 202.1.7.3: Packets: Sent = 4, Received = 2, Lost = 2 (50% loss), Approximate round trip times in milli-seconds: Minimum = 1331ms, Maximum = 1973ms, Average = 1652ms ======================================= THIRD PIN C:\Documents and Settings\user>ping gw1.ibllc.com.hk Pinging gw1.ibllc.com.hk [202.1.7.3] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Reply from 202.1.7.3: bytes=32 time=1457ms TTL=44 Ping statistics for 202.1.7.3: Packets: Sent = 4, Received = 1, Lost = 3 (75% loss), Approximate round trip times in milli-seconds: Minimum = 1457ms, Maximum = 1457ms, Average = 1457ms ================================================ I tried ADSL, FTTB, ISDN and 55.6 Modem, with the same results. If pin result can not explain why TWS disconnect from the server, the what will be possible reason & solution of my recent frequent TWS diesconnection from the IB server? TWS connection has been fairly stable until this July, I downgrade from version 8.48 to 8.43, and tried from two desktops and one laptop, but the things did not imporve. Just do not know what to do
Where are you pinging from joesan? Those are very bad results and the request timeouts suggest loss of packets which would potentially result in ib dropping out altogether. You need to talk to your ISP.
Suspect the ISP's route everything through ports on their proxy and sniff every packet in the hope of being able to direct requests to a local mirror - also latency from packets backing up as they cue them to fit down constricted bandwidth). All about saving on international bandwidth costs. It stinks, but not a lot you can do as they probably all do it.
This: http://www.pingplotter.com/download.html may help you locate the problem and give evidence of where the problem is if it is within your ISP's network and you need to deflect lies and fob offs - but you will probably find that the problem is a) caused at the state enterprise gateway and b) nobody at ISP knows what packet loss is