Hank Nussbacher <hank@att.net.il> wrote:
Why would 216.136.44.104 do something like this?
Aside from DNS glitch this traceroute has other funnies:
10 sl-inetconn-1-0-0-T3.sprintlink.net (144.228.207.46) [AS 1239] 200 msec 204 msec 208 msec 11 pa1-atm0-6-bbr01.alby.twtelecom.net (207.250.101.2) [AS 4323] 244 msec 264 msec 248 msec 12 pa1-atm0-5-acr01.alby.twtelecom.net (216.136.44.242) [AS 4323] 256 msec 252 msec 252 msec 13 learnl-ppp-1130-09-u242.alby.twtelecom.net (207.250.24.30) [AS 3857] 256 msec 260 msec 256 msec 14 ip104.44.136.216.in-addr.arpa (216.136.44.104) [AS 4323] 404 msec 400 msec 380 msec
Look at the ASNs, particluarly hops 12-13-14 :) --vadim
On Thu, 15 Jun 2000, Vadim Antonov wrote:
Hank Nussbacher <hank@att.net.il> wrote:
Why would 216.136.44.104 do something like this?
Aside from DNS glitch this traceroute has other funnies:
10 sl-inetconn-1-0-0-T3.sprintlink.net (144.228.207.46) [AS 1239] 200 msec 204 msec 208 msec 11 pa1-atm0-6-bbr01.alby.twtelecom.net (207.250.101.2) [AS 4323] 244 msec 264 msec 248 msec 12 pa1-atm0-5-acr01.alby.twtelecom.net (216.136.44.242) [AS 4323] 256 msec 252 msec 252 msec 13 learnl-ppp-1130-09-u242.alby.twtelecom.net (207.250.24.30) [AS 3857] 256 msec 260 msec 256 msec 14 ip104.44.136.216.in-addr.arpa (216.136.44.104) [AS 4323] 404 msec 400 msec 380 msec
Look at the ASNs, particluarly hops 12-13-14 :)
As a Time Warner Telecom data customer, I think I can help shed some light. In an attempt to have a "national" network, TWT bought inc.net. In doing so, they inherited their network, NOC, ASN, and address space. I've been assured that they are working diligently to consolidate their operations, but they're obviously not done yet. Pete -- Peter J. Templin, Jr., CCNA VP Networking On-Line Internet Services - URDirect.net A division of Global On-Line Computers 2414 Babcock Rd. Suite 106 templin@urdirect.net San Antonio, TX 78229 (210)692-9911
participants (2)
-
Pete Templin -
Vadim Antonov