On Wed, 15 Apr 2009, Blake Pfankuch wrote:
2 dvr-edge-05.inet.qwest.net (72.165.27.181) 27.696 ms 27.688 ms 28.022 ms 3 dvr-core-01.inet.qwest.net (205.171.10.89) 28.010 ms 28.001 ms 27.990 ms 4 * * 67.14.2.89 (67.14.2.89) 50.773 ms 5 xe-8-2-0.edge2.dallas3.level3.net (4.68.63.53) 51.120 ms xe-8-1-0.edge2.dallas3.level3.net (4.68.63.49) 51.107 ms 51.099 ms 6 vlan79.csw2.Dallas1.Level3.net (4.68.19.126) 56.763 ms 37.806 ms vlan89.csw3.Dallas1.Level3.net (4.68.19.190) 33.368 ms 7 ae-82-82.ebr2.Dallas1.Level3.net (4.69.136.145) 35.514 ms ae-72-72.ebr2.Dallas1.Level3.net (4.69.136.141) 44.125 ms ae-62-62.ebr2.Dallas1.Level3.net (4.69.136.137) 44.120 ms 8 ae-2.ebr1.Denver1.Level3.net (4.69.132.105) 50.913 ms 50.895 ms 50.522 ms 9 ge-6-0.hsa1.Denver1.Level3.net (4.68.107.3) 45.675 ms !H ge-6-1.hsa1.Denver1.Level3.net (4.68.107.67) 46.875 ms !H *
Thanks to all who replied. I should have actually reposted traces but it would have annoyed. I had experienced issues connecting to Level3.com, couldn't reach lg.level3 from a wide range of sites. I have a ticket on "watch" mode of sorts concerning a TDM switch having gone down in Connecticut. Just seems a little strange yet another client passing through an interchange with Level3 is now affected as well. I'll let them deal with their own provider. As far as I can tell from the ITSP side of things, I'm alright now. Anyone doing VoIP would have seen the Level3 hiccup up here (Stamford area'ish). =+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ J. Oquendo SGFA, SGFE, C|EH, CNDA, CHFI, OSCP "It takes 20 years to build a reputation and five minutes to ruin it. If you think about that, you'll do things differently." - Warren Buffett 227C 5D35 7DCB 0893 95AA 4771 1DCE 1FD1 5CCD 6B5E http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x5CCD6B5E