From usenix.org: 12-% traceroute -n 208.56.139.155
From other nets available to me:
Actually, me bad. It is the nameservers they use for their clients: ns5.behosting.com 208.56.139.155 ns6.behosting.com 208.56.138.142 I cannot reach either from many nets on the west coast, and the traceroutes die very early: traceroute to 208.56.139.155 (208.56.139.155), 30 hops max, 40 byte packets 1 131.106.3.254 0.677 ms 0.324 ms 0.310 ms 2 131.106.1.252 0.937 ms 0.971 ms 0.931 ms 3 * * * 4 * normally goes out: 1 gw.usenix.org (131.106.3.254) 0.561 ms 0.296 ms 0.260 ms 2 alternet-gw.usenix.ORG (131.106.1.252) 1.396 ms 1.024 ms 1.324 ms 3 twtwan (206.169.168.45) 235.612 ms 106.793 ms 156.533 ms 4 twtgw (206.169.155.13) 212.983 ms 154.202 ms 213.979 ms 5 ^C dist-02-so-0-0-0-0.okld.twtelecom.net (168.215.55.74) 176.927 ms 217.310 ms 173.318 ms traceroute to 208.56.139.155 (208.56.139.155), 64 hops max, 44 byte packets 1 megapath-gw (192.160.193.1) 3.408 ms 1.670 ms 1.634 ms 2 ip-64-139-1-1.dsl.sca.megapath.net (64.139.1.1) 11.782 ms 11.101 ms 10.642 ms 3 * * * traceroute to 208.56.139.155 (208.56.139.155), 64 hops max, 44 byte packets 1 (10.9.129.35) 3.734 ms 2.450 ms 2.311 ms 2 (10.8.5.73) 89.816 ms 169.081 ms 145.875 ms 3 (10.8.2.1) 210.021 ms 219.102 ms 280.200 ms 4 * * (10.x.x.x internal to my ISP - WCOM) traceroute to 208.56.139.155 (208.56.139.155), 30 hops max, 38 byte packets 1 sonic-gw (209.204.189.1) 14.490 ms 14.470 ms 12.984 ms 2 fast1-0-0.border.sr.sonic.net (208.201.224.194) 16.476 ms 24.872 ms 14.633 ms 3 fast4-1-0.border2.sr.sonic.net (64.142.0.26) 15.193 ms 14.675 ms 16.076 ms 4 serial1-0.gw.focal-sf.sonic.net (64.142.0.2) 17.359 ms 16.794 ms 15.017 ms 5 * * *
From the well:
traceroute to 208.56.139.155 (208.56.139.155) 30 hops max, 38 byte packets 1 gw.well.com (206.14.209.1) 2 ms 2 ms 1 ms 2 206.14.211.65 (206.14.211.65) 86 ms 1 ms 1 ms 3 206.14.211.65 (206.14.211.65) 1 ms (ttl=254!) !H * 1 ms (ttl=254!) !H -- -=[L]=-
On Wed, Sep 17, 2003 at 07:37:12AM -0700, Lou Katz wrote:
Actually, me bad. It is the nameservers they use for their clients: ns5.behosting.com 208.56.139.155 ns6.behosting.com 208.56.138.142
maybe call up alabanza and see what's up? from RIS: . No update is found in the database for 20030915. . Updates between 2003-09-16 00:00:00Z and 2003-09-16 23:59:59Z . . _________________________________________________________________ . . Type Prefix Time Peer Next HOP MED Origin AS path Community RRC ID . W 208.56.0.0/16 2003-09-16 17:05:30Z 198.32.200.125 0 0 IGP 0 Not configured MAE-West . . Updates between 2003-09-17 00:00:00Z and 2003-09-17 23:59:59Z . . _________________________________________________________________ . . Type Prefix Time Peer Next HOP MED Origin AS path Community RRC ID . A 208.56.0.0/16 2003-09-17 23:48:57Z 198.32.200.50 198.32.200.50 0 IGP 6066 701 7018 11022 Not configured MAE-West . W 208.56.0.0/16 2003-09-17 23:51:19Z 198.32.200.50 0 0 IGP 0 Not configured MAE-West 208.56.0.0 is: . OrgName: Alabanza, Inc. . OrgID: ALAB . Address: 10 E. Baltimore St. Suite 1300 . City: Baltimore . StateProv: MD . PostalCode: 21244 . Country: US . . NetRange: 208.56.0.0 - 208.56.255.255 . CIDR: 208.56.0.0/16 . NetName: ALABANZA-BALT-3 . NetHandle: NET-208-56-0-0-1 . Parent: NET-208-0-0-0-0 . NameServer: NS.ALABANZA.COM . NameServer: NS2.ALABANZA.COM . Comment: ADDRESSES WITHIN THIS BLOCK ARE NON-PORTABLE . RegDate: 1999-08-27 . Updated: 2000-05-15 . . TechHandle: TC12-ARIN . TechName: Cunningham, Thomas . TechPhone: +1-410-779-1400 . TechEmail: ipadmin@alabanza.com . . # ARIN WHOIS database, last updated 2003-09-16 19:15 -- Henry Yen Aegis Information Systems, Inc. Senior Systems Programmer Hicksville, New York
participants (2)
-
Henry Yen -
Lou Katz