|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical UUNET DALLAS <-> HOUSTON fubar
from what I can tell it seems that UUNET in Dallas,Houston is not doing well today. Any other data points on the net ?? Via verio link to dallas traceroute to www.uunet.net (199.170.0.30), 30 hops max, 40 byte packets 1 abq-rtr-01 (206.29.128.1) 0.675 ms 0.571 ms 0.413 ms 2 209-75-129-189.verio-wan-abq.verio.net (209.75.129.189) 2.623 ms 2.446 ms 6.282 ms 3 d3-3-0.r00.dllstx01.us.bb.verio.net (129.250.16.97) 51.483 ms 50.206 ms 50.343 ms 4 ATM3-0.BR1.DFW9.ALTER.NET (137.39.23.221) 51.204 ms 51.148 ms 51.079 ms 5 140.at-5-0-0.XR1.DFW9.ALTER.NET (152.63.98.122) 64.602 ms 51.599 ms 51.360 ms 6 * * * 7 * 132.at-5-0-0.TR1.DCA6.ALTER.NET (152.63.2.173) 569.456 ms * 8 * * 287.at-4-0-0.XR1.DCA1.ALTER.NET (152.63.33.213) 565.894 ms 9 195.ATM8-0-0.GW2.DCA1.ALTER.NET (146.188.161.33) 549.414 ms * 486.788 ms 10 * mas2-gw.customer.alter.net (157.130.82.118) 532.248 ms 533.614 ms via CW link to bloomington (I re-pref'd our traffic) traceroute whois.arin.net traceroute to whois.arin.net (192.149.252.22), 30 hops max, 40 byte packets 1 abq-rtr-01 (206.29.128.1) 0.553 ms 0.413 ms 0.412 ms 2 bordercore2-serial5-0-0-6.Bloomington.cw.net (166.48.176.25) 33.267 ms 27.469 ms 27.404 ms 3 corerouter1.Bloomington.cw.net (204.70.9.147) 34.783 ms 28.046 ms 27.738 ms 4 ATM1-0.BR1.LAX9.ALTER.NET (137.39.23.213) 394.744 ms 368.382 ms 411.652 ms 5 154.at-5-0-0.XR2.LAX9.ALTER.NET (152.63.113.22) 63.784 ms 63.977 ms 72.872 ms 6 190.ATM2-0.TR2.LAX2.ALTER.NET (152.63.112.218) 85.574 ms 79.273 ms 57.300 ms 7 111.ATM7-0.TR2.DCA8.ALTER.NET (146.188.138.197) 96.181 ms 95.849 ms 95.805 ms 8 196.at-4-0-0.XR2.TCO1.ALTER.NET (152.63.32.209) 96.515 ms 95.716 ms 95.763 ms 9 192.ATM6-0.GW5.TCO1.ALTER.NET (146.188.162.165) 100.648 ms 96.039 ms 95.927 ms 10 arin-gw.customer.ALTER.NET (157.130.35.6) 100.158 ms 99.815 ms 99.580 ms 11 rs2.arin.net (192.149.252.22) 102.249 ms^C |