IB site down (not TWS)

Quote from giles117:

If that were the case, everyone would be experiencing this problem.
More...

Well, that's kind of what IB told me, but what they couldn't tell me is why only interactivebrokers.com is affected, or why the problem is not specific to just one ISP/country/whatever.....
 
Quote from giles117:

If that were the case, everyone would be experiencing this problem. I am one of those that hasnt. I am sure there are more....

ISPs do iffy things. You'll be chugging along just fine and all of a sudden, no connection. then it will bounce back. or a certain side of the country will have server issues, and you'll feel the pinch...
More...

Not always... They could have multiple web servers and only one is having problems. They probably have multiple routers, switches, etc.... I don't think it's an ISP issue because here we use two, and either is the same, and at home I use a totally different one and it was the same as well. Also, I haven't complained to IB because eventually I get in (possibly server load, or switch/router errors?), so as far as they know, everything is fine here. I'm sure they'll eventually find the problem and fix it, however.

Also, every site I visit is fine except for IB's. Not to mention the connection to TWS is fine, which would be really weird if I was experiencing internet latency somewhere.

TNG
 
Some interesting troubleshooting here.

IDS gave you the URL using the IP address. That takes DNS out of the equation.

If some people can reach the URL (I can) and some people can't then its very unlikely that its a problem on IB's end.
 
Could somebody who can reach the ib .com site send us please a tracert to check whether sprintlink is the cause of this issue.
 
Here is my traceroute response....

traceroute to www.interactivebrokers.com (206.106.137.3), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.242 ms 1.075 ms 1.122 ms
2 * * *
3 ge-2-5-ur01.wallingford.pa.panjde.comcast.net (68.86.215.69) 14.892 ms 36.682 ms 60.655 ms
4 po-10-ur02.wallingford.pa.panjde.comcast.net (68.86.208.186) 11.128 ms 11.905 ms 31.613 ms
5 po-70-ar01.wallingford.pa.panjde.comcast.net (68.86.208.190) 9.572 ms 19.485 ms 9.841 ms
6 po-90-ar01.401nbroadst.pa.panjde.comcast.net (68.86.208.29) 17.615 ms 33.813 ms 9.069 ms
7 ge-3-0-cr01.torresdale.pa.core.comcast.net (68.86.211.14) 14.833 ms 20.406 ms 25.348 ms
8 12.118.114.9 (12.118.114.9) 17.216 ms 12.517 ms 18.902 ms
9 tbr1-p012301.phlpa.ip.att.net (12.123.137.210) 52.505 ms 26.559 ms 25.685 ms
10 tbr1-cl8.n54ny.ip.att.net (12.122.2.17) 21.458 ms 20.238 ms 32.388 ms
11 ggr3-ge40.n54ny.ip.att.net (12.122.81.9) 39.754 ms 14.521 ms 14.132 ms
12 sl-bb26-nyc-5-0.sprintlink.net (144.232.8.193) 33.016 ms 66.886 ms 19.621 ms
13 sl-bb25-nyc-8-0.sprintlink.net (144.232.13.189) 15.616 ms 16.534 ms 27.908 ms
14 sl-bb24-nyc-10-0.sprintlink.net (144.232.13.181) 208.890 ms 54.113 ms 22.025 ms
15 sl-gw27-nyc-15-0.sprintlink.net (144.232.7.26) 18.183 ms 14.860 ms 16.392 ms
16 sl-thllc-7-0.sprintlink.net (160.81.206.170) 38.577 ms 36.243 ms 20.263 ms

Seems you are having issues with the server at this IP address.

160.81.206.170
 
Quote from torel:

Could somebody who can reach the ib .com site send us please a tracert to check whether sprintlink is the cause of this issue.
More...
C:\>tracert interactivebrokers.com

Tracing route to interactivebrokers.com [206.106.137.3] over a maximum of 30 hops:

(first two hops removed for privacy)
3 3 ms 3 ms 3 ms so-5-0-1-0.BB-RTR2.RES.verizon-gni.net [130.81.28.197]
4 3 ms 3 ms 3 ms 0.so-7-0-0.XL2.IAD8.ALTER.NET [152.63.39.165]
5 8 ms 8 ms 8 ms 0.so-7-1-1.XT2.DCA5.ALTER.NET [152.63.32.33]
6 8 ms 8 ms 8 ms 0.so-7-0-0.BR1.DCA5.ALTER.NET [152.63.43.177]
7 9 ms 9 ms 9 ms sl-st22-ash-10-3.sprintlink.net [144.232.9.105]
8 11 ms 11 ms 11 ms sl-bb24-rly-13-0.sprintlink.net [144.232.20.188]
9 18 ms 18 ms 18 ms sl-bb23-nyc-10-0.sprintlink.net [144.232.20.182]
10 18 ms 18 ms 18 ms sl-gw27-nyc-14-0.sprintlink.net [144.232.7.22]
11 20 ms 20 ms 20 ms sl-thllc-7-0.sprintlink.net [160.81.206.170]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 ^C

Trace complete.

C:\>tracert 206.106.137.1

Tracing route to 206.106.137.1 over a maximum of 30 hops

3 3 ms 3 ms 3 ms so-5-0-1-0.BB-RTR2.RES.verizon-gni.net [130.81.28.197]
4 3 ms 3 ms 3 ms 0.so-7-0-0.XL2.IAD8.ALTER.NET [152.63.39.165]
5 8 ms 8 ms 8 ms 0.so-7-1-1.XT2.DCA5.ALTER.NET [152.63.32.33]
6 8 ms 8 ms 8 ms 0.so-7-0-0.BR1.DCA5.ALTER.NET [152.63.43.177]
7 9 ms 9 ms 9 ms 204.255.168.14
8 11 ms 10 ms 11 ms sl-bb24-rly-8-0.sprintlink.net [144.232.20.154]
9 18 ms 18 ms 18 ms sl-bb23-nyc-10-0.sprintlink.net [144.232.20.182]
10 18 ms 18 ms 18 ms sl-gw27-nyc-14-0.sprintlink.net [144.232.7.22]
11 21 ms 21 ms 21 ms 206.106.137.1

Trace complete.
C:\>ping interactivebrokers.com

Pinging interactivebrokers.com [206.106.137.3] with 32 bytes of data:

Request timed out.

Ping statistics for 206.106.137.3:
Packets: Sent = 1, Received = 0, Lost = 1 (100% loss),

C:\>ping 206.106.137.1

Pinging 206.106.137.1 with 32 bytes of data:
Reply from 206.106.137.1: bytes=32 time=21ms TTL=243
Reply from 206.106.137.1: bytes=32 time=20ms TTL=243
Reply from 206.106.137.1: bytes=32 time=20ms TTL=243
More...
Note that according to WhoIs the whole 206.106.137.0/24 net is registered to Timber Hill.
 
Quote from torel:

giles, GTS,

thank you! But I don't see the IP 206.106.137.3 of www.interactivebrokers.com at the end of your traceroute.

How can you reach this site then? Are you sure you see fresh contents and not only pages from the cache of your browser?
More...
206.106.137.3 is not responding to ping (icmp) therefore you wont see it in traceroute (that's why I did a separate ping test)

Accessing it for HTTP (tcp 80) is a completely separate issue.
 
You must log in or register to reply here.
Back
Top