I am unable to reach them via several different ISPs. It looks to my naive eyes like routes to them have vanished. Can anyone shed any light on this? -- -=[L]=-
Hello, Attempts to access behosting.com were successful from several different locations, which included ameritech and sprint. I'm not going to include traceroutes here (if you would like them, I can email them to you privately). What ISPs are you using to try and get to them? -------------------------- Brian Bruns The Summit Open Source Development Group Open Solutions For A Closed World / Anti-Spam Resources http://www.2mbit.com ICQ: 8077511 ----- Original Message ----- From: "Lou Katz" <lou@metron.com> To: <nanog@merit.edu> Sent: Wednesday, September 17, 2003 9:23 PM Subject: Route failures to behosting.com
I am unable to reach them via several different ISPs. It looks to my naive eyes like routes to them have vanished. Can anyone shed any light on this? -- -=[L]=-
On Wed, Sep 17, 2003 at 09:29:57AM -0400, Brian Bruns wrote:
Attempts to access behosting.com were successful from several different locations, which included ameritech and sprint. I'm not going to include traceroutes here (if you would like them, I can email them to you privately). What ISPs are you using to try and get to them?
behosting.com/www.behosting.com (aka 216.121.96.160) also accessible without problem from sprint and uunet.
----- Original Message ----- From: "Lou Katz" <lou@metron.com> To: <nanog@merit.edu> Sent: Wednesday, September 17, 2003 9:23 PM Subject: Route failures to behosting.com
I am unable to reach them via several different ISPs. It looks to my naive eyes like routes to them have vanished. Can anyone shed any light on this?
-- Henry Yen Aegis Information Systems, Inc. Senior Systems Programmer Hicksville, New York
Also accessible no problem from Qwest and Nlayer. -hc -- Sincerely, Haesu C. TowardEX Technologies, Inc. WWW: http://www.towardex.com E-mail: haesu@towardex.com Cell: (978) 394-2867 On Wed, Sep 17, 2003 at 09:35:54PM -0400, Henry Yen wrote:
On Wed, Sep 17, 2003 at 09:29:57AM -0400, Brian Bruns wrote:
Attempts to access behosting.com were successful from several different locations, which included ameritech and sprint. I'm not going to include traceroutes here (if you would like them, I can email them to you privately). What ISPs are you using to try and get to them?
behosting.com/www.behosting.com (aka 216.121.96.160) also accessible without problem from sprint and uunet.
----- Original Message ----- From: "Lou Katz" <lou@metron.com> To: <nanog@merit.edu> Sent: Wednesday, September 17, 2003 9:23 PM Subject: Route failures to behosting.com
I am unable to reach them via several different ISPs. It looks to my naive eyes like routes to them have vanished. Can anyone shed any light on this?
-- Henry Yen Aegis Information Systems, Inc. Senior Systems Programmer Hicksville, New York
At 09:35 PM 9/17/2003 -0400, Henry Yen wrote:
On Wed, Sep 17, 2003 at 09:29:57AM -0400, Brian Bruns wrote:
Attempts to access behosting.com were successful from several different locations, which included ameritech and sprint. I'm not going to include traceroutes here (if you would like them, I can email them to you privately). What ISPs are you using to try and get to them?
behosting.com/www.behosting.com (aka 216.121.96.160) also accessible without problem from sprint and uunet.
No problems from qwest or cw.
----- Original Message ----- From: "Lou Katz" <lou@metron.com> To: <nanog@merit.edu> Sent: Wednesday, September 17, 2003 9:23 PM Subject: Route failures to behosting.com
I am unable to reach them via several different ISPs. It looks to my naive eyes like routes to them have vanished. Can anyone shed any light on this?
-- Henry Yen Aegis Information Systems, Inc. Senior Systems Programmer Hicksville, New York
Looks like whomever holds the name server 208.56.139.155 etc is not announcing that route. So now, can we end this thread now? I think enough people replied already. [23:49:35][haesu@moosifer:~]$ traceroute 208.56.139.155 traceroute to 208.56.139.155 (208.56.139.155), 30 hops max, 40 byte packets 1 box02ce3-ed01-v305.twdx.net (65.124.16.1) 0.485 ms 0.545 ms 0.513 ms 2 box02jp5-cr01-g0-0.twdx.net (65.116.132.33) 0.19 ms 0.29 ms 0.145 ms 3 box02c75-br01-p3-0.twdx.net (65.116.132.1) 0.996 ms 1.005 ms 0.942 ms 4 box02c75-br01-p3-0.twdx.net (65.116.132.1) 0.916 ms !N * * 5 box02c75-br01-p3-0.twdx.net (65.116.132.1) 0.918 ms !N * 0.813 ms !N box02zbr-en02> sh ip bgp 208.56.139.155 % Network not in table haesu@moosifer:~]$ whois 208.56.139.155 OrgName: Alabanza, Inc. OrgID: ALAB Address: 10 E. Baltimore St. Suite 1300 City: Baltimore StateProv: MD PostalCode: 21244 Country: US [23:52:04][haesu@moosifer:~]$ whois -h whois.radb.net 208.56.139.155 % No entries found for the selected source(s). -hc -- Sincerely, Haesu C. TowardEX Technologies, Inc. WWW: http://www.towardex.com E-mail: haesu@towardex.com Cell: (978) 394-2867 On Wed, Sep 17, 2003 at 10:09:45PM -0400, Roy Bentley wrote:
At 09:35 PM 9/17/2003 -0400, Henry Yen wrote:
On Wed, Sep 17, 2003 at 09:29:57AM -0400, Brian Bruns wrote:
Attempts to access behosting.com were successful from several different locations, which included ameritech and sprint. I'm not going to include traceroutes here (if you would like them, I can email them to you privately). What ISPs are you using to try and get to them?
behosting.com/www.behosting.com (aka 216.121.96.160) also accessible without problem from sprint and uunet.
No problems from qwest or cw.
----- Original Message ----- From: "Lou Katz" <lou@metron.com> To: <nanog@merit.edu> Sent: Wednesday, September 17, 2003 9:23 PM Subject: Route failures to behosting.com
I am unable to reach them via several different ISPs. It looks to my naive eyes like routes to them have vanished. Can anyone shed any light on this?
-- Henry Yen Aegis Information Systems, Inc. Senior Systems Programmer Hicksville, New York
Thanks for the help. Apologies for keeping it going so long. End thread. -- -=[L]=-
participants (5)
-
Brian Bruns -
Haesu -
Henry Yen -
Lou Katz -
Roy Bentley