I'm seeing similar from residential FiOS in DC::<div><div>Jason-Sparkss-MacBook-Pro:~ jlsparks$ traceroute <a href="http://www.level3.com">www.level3.com</a></div><div>traceroute to <a href="http://www.level3.com">www.level3.com</a> (4.68.95.11), 64 hops max, 52 byte packets</div>
<div> 1 192.168.1.1 (192.168.1.1) 3.706 ms 0.796 ms 0.854 ms</div><div> 2 <a href="http://l100.washdc-vfttp-47.verizon-gni.net">l100.washdc-vfttp-47.verizon-gni.net</a> (96.255.98.1) 2.191 ms 1.793 ms 1.779 ms</div>
<div> 3 <a href="http://g4-0-1-747.washdc-lcr-07.verizon-gni.net">g4-0-1-747.washdc-lcr-07.verizon-gni.net</a> (130.81.59.152) 2.397 ms 2.125 ms 2.186 ms</div><div> 4 <a href="http://so-3-0-0-0.lcc1-res-bb-rtr1-re1.verizon-gni.net">so-3-0-0-0.lcc1-res-bb-rtr1-re1.verizon-gni.net</a> (130.81.29.0) 3.974 ms 3.023 ms 2.965 ms</div>
<div> 5 <a href="http://0.ae1.br1.iad8.alter.net">0.ae1.br1.iad8.alter.net</a> (152.63.32.141) 5.651 ms 3.790 ms</div><div> <a href="http://0.ae1.br2.iad8.alter.net">0.ae1.br2.iad8.alter.net</a> (152.63.34.21) 3.579 ms</div>
<div> 6 <a href="http://ae6.edge1.washingtondc4.level3.net">ae6.edge1.washingtondc4.level3.net</a> (4.68.62.133) 6.286 ms * *</div><div> 7 <a href="http://vlan90.csw4.washington1.level3.net">vlan90.csw4.washington1.level3.net</a> (4.69.149.254) 4.479 ms</div>
<div> <a href="http://vlan70.csw2.washington1.level3.net">vlan70.csw2.washington1.level3.net</a> (4.69.149.126) 10.478 ms</div><div> <a href="http://vlan90.csw4.washington1.level3.net">vlan90.csw4.washington1.level3.net</a> (4.69.149.254) 7.878 ms</div>
<div> 8 <a href="http://ae-71-71.ebr1.washington1.level3.net">ae-71-71.ebr1.washington1.level3.net</a> (4.69.134.133) 4.918 ms 4.653 ms</div><div> <a href="http://ae-61-61.ebr1.washington1.level3.net">ae-61-61.ebr1.washington1.level3.net</a> (4.69.134.129) 4.540 ms</div>
<div> 9 <a href="http://ae-8-8.ebr1.washington12.level3.net">ae-8-8.ebr1.washington12.level3.net</a> (4.69.143.218) 5.132 ms 5.234 ms 5.787 ms</div><div>10 <a href="http://ae-1-100.ebr2.washington12.level3.net">ae-1-100.ebr2.washington12.level3.net</a> (4.69.143.214) 5.241 ms 5.075 ms 87.833 ms</div>
<div>11 <a href="http://ae-6-6.ebr2.chicago2.level3.net">ae-6-6.ebr2.chicago2.level3.net</a> (4.69.148.146) 25.148 ms 24.995 ms 23.701 ms</div><div>12 <a href="http://ae-1-100.ebr1.chicago2.level3.net">ae-1-100.ebr1.chicago2.level3.net</a> (4.69.132.113) 24.656 ms 24.834 ms 24.737 ms</div>
<div>13 <a href="http://ae-3-3.ebr2.denver1.level3.net">ae-3-3.ebr2.denver1.level3.net</a> (4.69.132.61) 50.896 ms 53.748 ms 54.740 ms</div><div>14 <a href="http://ge-9-1.hsa1.denver1.level3.net">ge-9-1.hsa1.denver1.level3.net</a> (4.68.107.99) 50.641 ms 53.752 ms 50.221 ms</div>
<div>15 4.68.94.27 (4.68.94.27) 51.479 ms 53.397 ms 51.894 ms</div><div>16 4.68.94.33 (4.68.94.33) 52.956 ms 52.233 ms 52.237 ms</div><div>17 * * *</div><div>18 * * *</div><div><br></div><div><br></div><br><div class="gmail_quote">
On Thu, Dec 16, 2010 at 5:06 PM, Robert Johnson <span dir="ltr"><<a href="mailto:fasterfourier@gmail.com">fasterfourier@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
It seems traffic attempting to pass through Level3's network in the<br>
Washington, DC area is getting lost in the abyss. Here's a trace from<br>
VZ residential FIOS to <a href="http://www.level3.com" target="_blank">www.level3.com</a>:<br>
<br>
Tracing route to <a href="http://www.level3.com" target="_blank">www.level3.com</a> [4.68.95.11]<br>
over a maximum of 30 hops:<br>
<br>
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.3.254]<br>
2 7 ms 6 ms 6 ms <a href="http://L100.BLTMMD-VFTTP-40.verizon-gni.net" target="_blank">L100.BLTMMD-VFTTP-40.verizon-gni.net</a> [96.244.79.<br>
1]<br>
3 11 ms 8 ms 9 ms <a href="http://G10-0-1-440.BLTMMD-LCR-04.verizon-gni.net" target="_blank">G10-0-1-440.BLTMMD-LCR-04.verizon-gni.net</a> [130.8<br>
1.110.158]<br>
4 13 ms 11 ms 14 ms <a href="http://so-2-0-0-0.PHIL-BB-RTR2.verizon-gni.net" target="_blank">so-2-0-0-0.PHIL-BB-RTR2.verizon-gni.net</a> [130.81.<br>
28.82]<br>
5 21 ms 19 ms 19 ms <a href="http://so-7-1-0-0.RES-BB-RTR2.verizon-gni.net" target="_blank">so-7-1-0-0.RES-BB-RTR2.verizon-gni.net</a> [130.81.1<br>
9.106]<br>
6 20 ms 19 ms 19 ms <a href="http://0.ae2.BR2.IAD8.ALTER.NET" target="_blank">0.ae2.BR2.IAD8.ALTER.NET</a> [152.63.34.73]<br>
7 16 ms 16 ms 18 ms <a href="http://ae7.edge1.washingtondc4.level3.net" target="_blank">ae7.edge1.washingtondc4.level3.net</a> [4.68.62.137]<br>
8 26 ms 19 ms 17 ms <a href="http://vlan80.csw3.Washington1.Level3.net" target="_blank">vlan80.csw3.Washington1.Level3.net</a> [4.69.149.190<br>
]<br>
9 22 ms 24 ms 26 ms <a href="http://ae-92-92.ebr2.Washington1.Level3.net" target="_blank">ae-92-92.ebr2.Washington1.Level3.net</a> [4.69.134.1<br>
57]<br>
10 * * * Request timed out.<br>
<br>
Anyone else?<br>
<br>
_______________________________________________<br>
Outages mailing list<br>
<a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
</blockquote></div><br></div>