traceroute to lycos dies at C&W in Cleveland, what's up?

Mailman List Mirror (Read Only)
1

Anyone know about this? Traceroute goes from here through Verio Mid-America
(first to Cleveland, then to Chicago), then to C&W Willow Springs (Chicago),
then back here to C&W North Royalton (Cleveland again).

Then the traceroute dies....

Did someone pull the plug on a router or something?

                                                  Packets Pings
Hostname %Loss Rcv Snt Best Avg
Worst
1. fe0-0.core1.cleveland.nacs.net 0% 8 8 11 14
19
2. serial3-4.csr1.cv.oh.verio.net 0% 8 8 8 12
19
3. fddi9-0.csr0.cv.oh.verio.net 0% 8 8 8 15
27
4. serial1-0.csr8.or.il.verio.net 0% 8 8 21 29
41
5. hssi1-0.csr7.or.il.verio.net 0% 8 8 21 33
46
6. atm8-0.csr6.or.il.verio.net 0% 8 8 21 33
46
7. bordercore3-hssi0-0-0.WillowSprings.cw.net 0% 8 8 21 35
54
8. bordercore2.NorthRoyalton.cw.net 0% 8 8 30 39
56
9. ???
10. ???
11. ???
12. ???
13. ???
14. ???
15. ???
16. ???
17. ???
18. ???
19. ???
20. ???
21. ???
22. ???
23. ???
24. ???
25. ???

2

Steve, what CIDR network are you running the trace to?

3

207.77.90.0/23. The specific address is 207.77.91.112,
faust.eng.pgh.lycos.com, which judging from the domain name, is probably at
their HQ out in Pittsburgh.

I have been informed by someone else that this happened due to an apparent
misconfiguration at Lycos. I'm forwarding that e-mail on to Devin Anderson.