anyone know what is going on over at uu?
seeing problems all over...
3 <10 ms <10 ms <10 ms 216.79.187.254
4 <10 ms 10 ms <10 ms 172.25.57.5
5 <10 ms 10 ms <10 ms 205.152.37.184
6 <10 ms 10 ms 10 ms 500.POS2-0.GW11.ATL5.ALTER.NET
[157.130.76.97]
7 10 ms 10 ms <10 ms 0.so-2-1-0.XL2.ATL5.ALTER.NET
[152.63.85.38]
8 <10 ms 10 ms 10 ms POS7-0.BR2.ATL5.ALTER.NET [152.63.82.193]
9 * * * Request timed out.
10 * * * Request timed out.
Best regards,
Bryan Heitman
Interland, Inc.
wow.. what are you trying to get to? This looks like it entered 701 on
hop 6 and exited at hop 8 to some other network which sttms to have some
delivery problems of its own.
--Chris
(chris@uu.net)
anyone know what is going on over at uu?
seeing problems all over...
> 3 <10 ms <10 ms <10 ms 216.79.187.254
> 4 <10 ms 10 ms <10 ms 172.25.57.5
> 5 <10 ms 10 ms <10 ms 205.152.37.184
> 6 <10 ms 10 ms 10 ms 500.POS2-0.GW11.ATL5.ALTER.NET
> [157.130.76.97]
> 7 10 ms 10 ms <10 ms 0.so-2-1-0.XL2.ATL5.ALTER.NET
> [152.63.85.38]
> 8 <10 ms 10 ms 10 ms POS7-0.BR2.ATL5.ALTER.NET [152.63.82.193]
> 9 * * * Request timed out.
> 10 * * * Request timed out.
Knowing source and destination would help. It appears that a
traceroute from some Bellsouth node dies out somewhere... what's
the destination?
Eddy
We're starting to see the same issues with uunet, again. Anyone else
seeing this? Trying to reach Qwest...
traceroute to 63.146.190.1 (63.146.190.1), 30 hops max, 38 byte packets
1 esc-lp2-gw.e-solutionscorp.com (63.118.220.1) 1.167 ms 1.163 ms
1.142 ms
2 500.Serial2-10.GW1.TPA2.ALTER.NET (157.130.149.9) 1.097 ms 1.059 ms
1.044 ms
3 161.at-1-0-0.XL4.ATL1.ALTER.NET (152.63.81.190) 13.839 ms 14.108 ms
16.638 ms
4 0.so-3-1-0.XL2.ATL5.ALTER.NET (152.63.0.238) 14.370 ms 14.587 ms
14.553 ms
5 POS7-0.BR2.ATL5.ALTER.NET (152.63.82.193) 13.928 ms 14.099 ms
14.053 ms
6 * * *
...
Thanks,
--Chad