Jeff, That's not packet loss. Level3 does not prioritize ping so their hops usually do look like that. If you notice all the next hops after show 0% to the endpoint, on both sides of your trace, therefore no packet loss followed through. On Fri, Apr 22, 2016 at 8:02 AM, Jeff Agle via Outages <outages@outages.org> wrote:

Anyone else seeing peering issues / loss in Level3 this morning? The below is to/from Eastern Canada. Keep getting route changes in the path as well.

Hop Sent PL% Min Max Avg Host Name/IP 1 1535 0 0.58 22.72 0.87 192.168.224.1 [192.168.224.1] 2 1535 0 0.83 284.45 19.79 142.166.210.153 [142.166.210.153] 3 765 0 1.31 202.85 17.73 142.166.211.113 [142.166.211.113] 4 775 0 18.50 289.86 34.47 207.231.227.53 [207.231.227.53] 5 771 0 16.26 278.12 34.58 ae52.edge1.toronto2.level3.net [4.31.208.9] 6 1532 90 84.42 289.61 94.59 ae-1-60.ear1.sanjose1.level3.net [4.69.152.23] <--------- 7 1532 90 84.40 304.22 93.41 ae-1-60.ear1.sanjose1.level3.net [4.69.152.23] <-------- 8 1535 0 84.62 416.69 100.82 one-communi.ear1.sanjose1.level3.net [4.15.122.98] 9 1535 0 83.31 410.75 98.50 user-uinjs2k.biz.mindspring.com [165.121.240.84] 10 1535 0 84.63 406.80 97.94 66.32.80.116 [66.32.80.116] 11 1535 0 84.63 367.45 101.48 199.180.64.8 [199.180.64.8]

Hop Sent PL% Min Max Avg Host Name / IP 1 299 0 1 3.99 1.75 108.59.240.61 [108.59.240.61] 2 299 0 10.44 31.52 13.29 165.121.238.180 [165.121.238.180] 3 299 0 10.32 29.26 12.99 209.178.150.68 [209.178.150.68] 4 297 11 10 2437.3 74.79 5-1-34.ear2.newyork1.level3.net [4.35.90.65] <---------- 5 299 0 10.46 14.35 10.99 4.71.230.102 [4.71.230.102] 6 299 0 26 30.17 26.82 be5.cr01.stjh.nb.aliant.net [207.231.227.113] 7 299 0 25.76 40.32 30.25 loop0.1kw.ba06.stjh.nb.aliant.net [142.166.182.14]

~jeff

_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages