Hey folks.
I'm working with my friends at National Public Radio. They're having
network problems, and I'm not sure the correct people at UUNet to report
this anomaly to. The answer NPR got from UUNet was: MFS trouble in
Dallas. Does that make sense?any suggestions?
thanks in advance. sorry for the interruption.
# /usr/local/bin/traceroute npr.org
traceroute to npr.org (199.0.132.69), 30 hops max, 40 byte packets
1 router.butterfly.net (199.73.40.1) 7 ms 5 ms 3 ms
2 s0.router.clark.net (199.73.41.254) 12 ms 15 ms 12 ms
3 sl-dc-1-S19-T1.sprintlink.net (144.228.4.1) 19 ms 29 ms 17 ms
4 sl-dc-8-F0/0.sprintlink.net (144.228.20.8) 21 ms 19 ms 17 ms
5 sl-mae-e-H2/0-T3.sprintlink.net (144.228.10.42) 26 ms 18 ms 19 ms
6 Vienna1.VA.Alter.Net (192.41.177.249) 26 ms 297 ms *
7 sl-mae-e-F0/0.sprintlink.net (192.41.177.241) 22 ms 31 ms 44 ms
8 Vienna1.VA.Alter.Net (192.41.177.249) 62 ms 87 ms *
9 sl-mae-e-F0/0.sprintlink.net (192.41.177.241) 37 ms 36 ms 28 ms
10 Vienna1.VA.Alter.Net (192.41.177.249) 63 ms 83 ms 77 ms
11 sl-mae-e-F0/0.sprintlink.net (192.41.177.241) 21 ms 32 ms 27 ms
12 Vienna1.VA.Alter.Net (192.41.177.249) 40 ms 50 ms 68 ms
13 sl-mae-e-F0/0.sprintlink.net (192.41.177.241) 33 ms 19 ms 31
Well, at a zero-level information point (which is all I have from here 
this looks like Sprintlink thinks that network is reachable via Alternet,
and Alternet thinks it is reachable via Sprintlink.
Thus the looping. I'd contact the respective NOCs and let them hash it out.
At least one of these two is (obviously) wrong.