--- frnkblk@iname.com wrote: Funny how when you look at: https://www.sprint.net/performance/ everything seems OK, but IHR reports differently. ;) ------------------------------------ It's coming and going. Here's a traceroute from my border router to sprint.net from Hawaii across Qwest. But right afterward the site was reachable. A:WPHU7710# traceroute router 1500 208.24.22.50 traceroute to 208.24.22.50, 30 hops max, 40 byte packets 1 67.129.94.17 (67.129.94.17) <10 ms <10 ms <10 ms 2 205.171.14.181 (205.171.14.181) 70 ms 70 ms 70 ms 3 67.14.34.18 (67.14.34.18) 70 ms 70 ms 90 ms 4 205.171.233.30 (205.171.233.30) 100 ms 70 ms 70 ms 5 0.0.0.0 (0.0.0.0) * * * 6 0.0.0.0 (0.0.0.0) * * * 7 0.0.0.0 (0.0.0.0) * * * 8 0.0.0.0 (0.0.0.0) * * * 9 0.0.0.0 (0.0.0.0) * * * 10 144.232.0.108 (144.232.0.108) 150 ms 160 ms 160 ms 11 144.223.33.34 (144.223.33.34) 140 ms 150 ms 130 ms 12 0.0.0.0 (0.0.0.0) * * * 13 0.0.0.0 (0.0.0.0) * * * 14 0.0.0.0 (0.0.0.0) * * * 15 0.0.0.0 (0.0.0.0) * * * 16 0.0.0.0 (0.0.0.0) * * * 17 0.0.0.0 (0.0.0.0) * * * 18 0.0.0.0 (0.0.0.0) * ^C Eventhough the site's now reachable, I can't traceroute to it: A:WPHU7710# traceroute router 1500 208.24.22.50 traceroute to 208.24.22.50, 30 hops max, 40 byte packets 1 67.129.94.17 (67.129.94.17) 10 ms <10 ms <10 ms 2 205.171.14.181 (205.171.14.181) 70 ms 70 ms 80 ms 3 67.14.34.18 (67.14.34.18) 70 ms 90 ms 70 ms 4 205.171.233.30 (205.171.233.30) 80 ms 70 ms 70 ms 5 63.146.26.194 (63.146.26.194) 70 ms 70 ms 100 ms 6 144.232.9.59 (144.232.9.59) 80 ms 90 ms 70 ms 7 0.0.0.0 (0.0.0.0) * * * 8 144.232.9.65 (144.232.9.65) 100 ms 100 ms 100 ms 9 144.232.20.147 (144.232.20.147) 130 ms 130 ms 130 ms 10 144.232.0.108 (144.232.0.108) 130 ms 130 ms 130 ms 11 144.223.33.34 (144.223.33.34) 130 ms 130 ms 130 ms 12 0.0.0.0 (0.0.0.0) * * * 13 0.0.0.0 (0.0.0.0) * * * 14 0.0.0.0 (0.0.0.0) * * * 15 0.0.0.0 (0.0.0.0) * * * 16 0.0.0.0 (0.0.0.0) * * * 17 0.0.0.0 (0.0.0.0) * ^C scott