From your traceroute, you ascertain that the traffic is traversing the UUNET Backbone and is stopping just past the edge of the UUNET GW (Gateway) router as it leaves the UUNET Backbone.
Thanks, Adam -----Original Message----- From: McBurnett, Jim [mailto:jmcburnett@msmgmt.com] Sent: Tuesday, March 11, 2003 8:43 AM To: chuck goolsbee; nanog@merit.edu Subject: RE: Issue with 208.192.0.0/8 - 208.196.93.0/24? Is anyone from Alter.net lurking? Just for grins I went to the DIGEX looking glass and I could not ping it from MAE-Central, PAIX , MAE-East and also from AT&T Cerf router.... below are some of the traces.. Always dies on Alter... I wonder..... Alter? route-server>trac 208.196.93.204 Type escape sequence to abort. Tracing the route to ecobeauty.org (208.196.93.204) 1 mdf1-gsr12-1-gig-1-1.lax1.attens.net (12.129.192.237) [AS 17233] 0 msec 4 msec 0 msec 2 mdf1-gsr12-1-gig-1-1.lax1.attens.net (12.129.192.237) [AS 17233] 0 msec 0 msec 0 msec 3 gar3-p320.la2ca.ip.att.net (12.122.255.249) [AS 7018] 0 msec 4 msec 0 msec 4 gbr5-p90.la2ca.ip.att.net (12.123.28.193) [AS 7018] 4 msec 0 msec 0 msec 5 tbr2-p013501.la2ca.ip.att.net (12.122.11.153) [AS 7018] 4 msec 0 msec 4 msec 6 ggr1-p3100.la2ca.ip.att.net (12.122.11.222) [AS 7018] 0 msec 4 msec 4 msec 7 POS4-3.BR1.LAX9.ALTER.NET (204.255.168.61) [AS 701] 4 msec 4 msec 4 msec 8 0.so-0-1-0.XL2.LAX9.ALTER.NET (152.63.113.18) [AS 701] 4 msec 4 msec 4 msec 9 0.so-0-0-0.TL2.LAX9.ALTER.NET (152.63.115.146) [AS 701] 4 msec 4 msec 4 msec 10 0.so-6-0-0.TL2.NYC9.ALTER.NET (152.63.13.10) [AS 701] 76 msec 76 msec 76 msec 11 0.so-3-0-0.XL2.NYC1.ALTER.NET (152.63.29.113) [AS 701] 76 msec 76 msec 76 msec 12 0.so-0-0-0.XR2.NYC1.ALTER.NET (152.63.19.97) [AS 701] 76 msec 76 msec 76 msec 13 208.ATM7-0.GW11.NYC1.ALTER.NET (152.63.29.189) [AS 701] 76 msec 80 msec 76 mse c 14 * * * and it dies.. 03/11/03 08:28:24 Fast traceroute 208.196.93.204 Trace 208.196.93.204 ... 1 66.191.223.2 0ms 0ms 0ms TTL: 0 (cpe-66-191-223-002.spart.sc.charter.com ok) 2 66.168.32.41 0ms 0ms 0ms TTL: 0 (cpe-66-168-32-041.spart.sc.charter.com ok) 3 12.123.21.78 10ms 0ms 0ms TTL: 0 (gbr6-p80.attga.ip.att.net bogus rDNS: host not found [authoritative]) 4 12.122.12.25 10ms 0ms 0ms TTL: 0 (tbr1-p013601.attga.ip.att.net bogus rDNS: host not found [authoritative]) 5 12.122.12.30 0ms 10ms 0ms TTL: 0 (ggr1-p340.attga.ip.att.net bogus rDNS: host not found [authoritative]) 6 204.255.174.149 0ms 10ms 10ms TTL: 0 (POS5-2.BR2.ATL5.ALTER.NET ok) 7 152.63.82.194 10ms 0ms 10ms TTL: 0 (0.so-2-3-0.XL2.ATL5.ALTER.NET ok) 8 152.63.10.106 0ms 10ms 10ms TTL: 0 (0.so-0-0-0.TL2.ATL5.ALTER.NET ok) 9 152.63.146.42 20ms 20ms 20ms TTL: 0 (0.so-7-0-0.TL2.DCA6.ALTER.NET ok) 10 152.63.34.130 20ms 20ms 20ms TTL: 0 (0.so-5-0-0.CL2.DCA1.ALTER.NET ok) 11 152.63.42.110 30ms 20ms 20ms TTL: 0 (194.at-4-0-0.CL2.PHL1.ALTER.NET ok) 12 152.63.38.201 20ms 20ms 30ms TTL: 0 (POS7-0.GW6.PHL1.ALTER.NET ok) And away to the bit bucket...
-----Original Message----- From: chuck goolsbee [mailto:chucklist@forest.net] Sent: Monday, March 10, 2003 10:14 PM To: nanog@merit.edu Subject: Issue with 208.192.0.0/8 - 208.196.93.0/24?
Forgive the intrusion...
We have a customer who uses some merchant services off of 208.196.93.204, which seems to be unreachable via any location I try. Emails to UUnet's NOC are unaswered and the guy I talked to on the phone @ UU wouldn't open a ticket because I'm not a customer (but his traces were dying in the same place as mine:
207.ATM6-0.GW11.NYC1.ALTER.NET (152.63.29.185))
Can anybody out there hit that IP (208.196.93.204) at the moment? Or indeed much of anything in that /8?
-- --chuck goolsbee geek wrangler, digital.forest inc, bothell, wa <http://www.forest.net>