The route's toast from MCI also, but Alternet seems to have a route.
trc www.cisco.com traceroute to cio-sys.cisco.com (192.31.7.130), 30 hops max, 40 byte packets 1 krypton-Ethernet0-1.Cary.mci.net (204.70.140.2) 2 ms 2 ms 2 ms 2 border7-serial4-0.Washington.mci.net (204.70.77.101) 18 ms 15 ms 15 ms 3 * core2-fddi-0.Washington.mci.net (204.70.74.49) 16 ms 15 ms 4 barrnet.SanFrancisco.mci.net (166.48.19.250) 101 ms 88 ms 101 ms 5 barrnet.SanFrancisco.mci.net (166.48.19.250) 86 ms 88 ms 86 ms 6 su-pr2.bbnplanet.net (131.119.0.218) 89 ms 92 ms 88 ms 7 * * * 8 * * *
This appears to have been due to bogus MEDs that we were receiving from cisco via EBGP. Some reason you guys don't believe in sending mail to our NOC? FWIW, they don't monitor the NANOG mailing list and I don't they should -- it's not the right place for trouble reports... In any event, I've kludged a fix for this problem pending proper resolution (i.e. fixing it at the source). --jhawk (who really has better things to do with his Sunday afternoons...)