I can confirm similar behavior for the Washington area 4.2.2.2 following a different route: 4 ae-92-92.ebr2.Washington1.Level3.net (4.69.134.157) 2.020 ms 2.016 ms ae-62-62.ebr2.Washington1.Level3.net (4.69.134.145) 2.078 ms 5 ae-5-5.ebr2.Washington12.Level3.net (4.69.143.222) 2.476 ms ae-8-8.ebr1.Washington12.Level3.net (4.69.143.218) 2.830 ms ae-5-5.ebr2.Washington12.Level3.net (4.69.143.222) 2.534 ms 6 ae-2-52.edge2.Washington12.Level3.net (4.69.146.195) 2.650 ms 2.309 ms ae-1-51.edge2.Washington12.Level3.net (4.69.146.163) 2.463 ms 7 b.resolvers.Level3.net (4.2.2.2) 757.921 ms 757.779 ms 757.745 ms --- 4.2.2.2 ping statistics --- 50 packets transmitted, 38 received, 24% packet loss, time 28047ms rtt min/avg/max/mdev = 1.311/128.988/1728.583/419.168 ms, pipe 4 On Mon, Nov 5, 2012 at 11:53 AM, Seth Mattinen <sethm@rollernet.us> wrote:
On 11/5/12 8:48 AM, Josh Luthman wrote:
I specified Washington, presuming at least a few others are using that location.
Sorry, your original message didn't specify only responses from a specific geographic area.
~Seth _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
-- Best Regards, Brandon W. Tier 3 System Administrator InMotion Hosting Inc. 888-321-4678 757-416-6575 (Int'l) NEW: 24x7 EMAIL and PHONE Technical Support Did you know? We'll Build, Update and Promote Your Site for You! Visit www.inmotionhosting.com/webdesign Answers to commonly asked questions, as well as other useful tools, can be found at http://support.inmotionhosting.com How am I doing? Please feel free to email my manager at manager_feedback@inmotion.net