
We are seeing consistent issues with connectivity which appear to originate at Level3 in Dallas ... Don't think it's related to our particular route announcements from ASN 20208 .... please see below :traceroute smithbarney.com *from 64.72.86.254* traceroute: Warning: smithbarney.com has multiple addresses; using 192.193.224.16 traceroute to smithbarney.com (192.193.224.16), 64 hops max, 40 byte packets 1 64-72-86-249 (64.72.86.249) 0.550 ms 0.554 ms 0.452 ms 2 204-15-4-241-static (204.15.4.241) 2.598 ms 3.343 ms 2.202 ms 3 webjog-hvdn.customer.hvdata.net (64.72.65.249) 5.099 ms 4.866 ms 5.199 ms 4 nwbrnynwj91-ge-7-1-7.lightower.net (72.22.160.199) 4.725 ms 5.016 ms 4.458 ms 5 hpjtnyxbj21-xe-2-3-0.lightower.net (72.22.160.103) 5.721 ms 3.679 ms 4.323 ms 6 pghknyshj91-xe-7-3-0.lightower.net (72.22.160.104) 5.973 ms 6.148 ms 5.320 ms 7 pghknyshj41-ae0-66.lightower.net (72.22.160.159) 5.719 ms 10.005 ms 5.828 ms 8 bstpmallj42-xe-0-2-0.lightower.net (72.22.160.149) 12.092 ms 12.879 ms 12.094 ms 9 xe-10-1-0.bar2.Boston1.Level3.net (4.53.54.5) 15.814 ms 11.628 ms 11.824 ms 10 ae-8-8.ebr1.NewYork1.Level3.net (4.69.140.98) 16.216 ms 17.513 ms 20.181 ms 11 ae-91-91.csw4.NewYork1.Level3.net (4.69.134.78) 24.959 ms 18.505 ms 16.826 ms 12 ae-74-74.ebr4.NewYork1.Level3.net (4.69.134.117) 22.706 ms ae-84-84.ebr4.NewYork1.Level3.net (4.69.134.121) 23.061 ms ae-94-94.ebr4.NewYork1.Level3.net (4.69.134.125) 35.255 ms 13 ae-3.ebr2.Dallas1.Level3.net (4.69.137.121) 57.115 ms 68.668 ms 58.914 ms 14 ge-7-0-70.ipcolo1.Dallas1.Level3.net (4.69.145.110) 53.817 ms ge-6-0-60.ipcolo1.Dallas1.Level3.net (4.69.145.46) 54.425 ms 53.667 ms 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * Tracing route to 174-143-170-178.static.cloud-ips.com [174.143.170.178] *from 204.15.4.2* over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 204-15-4-1-static.webjogger.net [204.15.4.1] 2 1 ms 1 ms 1 ms 172.20.5.1 3 31 ms 3 ms 3 ms 204-15-4-241-static.webjogger.net [204.15.4.241] 4 5 ms 5 ms 4 ms webjog-hvdn.customer.hvdata.net [64.72.65.249] 5 4 ms 6 ms 4 ms nwbrnynwj91-ge-7-1-7.lightower.net [72.22.160.199] 6 5 ms 5 ms 5 ms hpjtnyxbj21-xe-2-3-0.lightower.net [72.22.160.103] 7 7 ms 6 ms 6 ms pghknyshj91-xe-7-3-0.lightower.net [72.22.160.104] 8 7 ms 6 ms 7 ms pghknyshj41-ae0-66.lightower.net [72.22.160.159] 9 12 ms 13 ms 39 ms bstpmallj42-xe-0-2-0.lightower.net [72.22.160.149] 10 19 ms 14 ms 12 ms xe-10-1-0.bar2.Boston1.Level3.net [4.53.54.5] 11 16 ms 18 ms 17 ms ae-8-8.ebr1.NewYork1.Level3.net [4.69.140.98] 12 17 ms 17 ms 18 ms ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70] 13 * * * Request timed out. 14 64 ms 66 ms 63 ms ae-3.ebr2.Dallas1.Level3.net [4.69.137.121] 15 * 54 ms 54 ms ae-4-90.edge2.Dallas3.Level3.net [4.69.145.204] 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. Adam -- Adam Greene Webjogger Internet Services http://www.webjogger.net (845) 757-4000

The site is up and functional on both of their IP's. Appears their firewall is blocking traceroute and icmp. Their IP responds to port 80 requests. I am able to access using a web browser as well, using the IP address. smithbarney.com has address 192.193.224.16 smithbarney.com has address 192.193.20.105 Interesting ports on salomonsmithbarney.com (192.193.224.16): PORT STATE SERVICE 80/tcp open http Interesting ports on salomonsmithbarney.com (192.193.20.105): PORT STATE SERVICE 80/tcp open http -- Matthew Adam Greene wrote:
We are seeing consistent issues with connectivity which appear to originate at Level3 in Dallas ...
Don't think it's related to our particular route announcements from ASN 20208 ....
please see below

Yes, it seems that as of ~1:30pm or so things were more or less back to normal ... On 10/29/2009 1:38 PM, Matthew Walker wrote:
The site is up and functional on both of their IP's. Appears their firewall is blocking traceroute and icmp. Their IP responds to port 80 requests. I am able to access using a web browser as well, using the IP address.
smithbarney.com has address 192.193.224.16 smithbarney.com has address 192.193.20.105
Interesting ports on salomonsmithbarney.com (192.193.224.16): PORT STATE SERVICE 80/tcp open http
Interesting ports on salomonsmithbarney.com (192.193.20.105): PORT STATE SERVICE 80/tcp open http
-- Matthew
Adam Greene wrote:
We are seeing consistent issues with connectivity which appear to originate at Level3 in Dallas ...
Don't think it's related to our particular route announcements from ASN 20208 ....
please see below
_______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (2)
-
Adam Greene
-
Matthew Walker