It seems traffic attempting to pass through Level3's network in the Washington, DC area is getting lost in the abyss. Here's a trace from VZ residential FIOS to www.level3.com: Tracing route to www.level3.com [4.68.95.11] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.3.254] 2 7 ms 6 ms 6 ms L100.BLTMMD-VFTTP-40.verizon-gni.net [96.244.79. 1] 3 11 ms 8 ms 9 ms G10-0-1-440.BLTMMD-LCR-04.verizon-gni.net [130.8 1.110.158] 4 13 ms 11 ms 14 ms so-2-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81. 28.82] 5 21 ms 19 ms 19 ms so-7-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.1 9.106] 6 20 ms 19 ms 19 ms 0.ae2.BR2.IAD8.ALTER.NET [152.63.34.73] 7 16 ms 16 ms 18 ms ae7.edge1.washingtondc4.level3.net [4.68.62.137] 8 26 ms 19 ms 17 ms vlan80.csw3.Washington1.Level3.net [4.69.149.190 ] 9 22 ms 24 ms 26 ms ae-92-92.ebr2.Washington1.Level3.net [4.69.134.1 57] 10 * * * Request timed out. Anyone else?