I had done this earlier, forgot to paste it, current results from Tustin, CA to 4.2.2.2 I also have presence in One Wilshire and 800 S Hope, I don't think we see the level3 issue there. I think the route has to do with Tustin > LA, every trace that has replied to this thread has been through an alternate route. Thanks. ---- statistics ---- 50 packets transmitted, 43 packets received, 14% packet loss rtt min/avg/median/max/mdev/stddev = 16/18.698/20/28/1.503/2.69 ms 50 packets transmitted, 44 packets received, 12% packet loss rtt min/avg/median/max/mdev/stddev = 16/20.727/20/44/1.933/6.283 ms On 3/11/2014 9:41 AM, Jeremy Chadwick wrote:
Does L3's LG come in handy for reproducing the issue? It might not given how packets flow (e.g. the loss is across a specific interface), but you might spend 15 minutes or so poking at it: