<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I had done this earlier, forgot to paste it, current results from
Tustin, CA to 4.2.2.2<br>
<br>
I also have presence in One Wilshire and 800 S Hope, I don't think
we see the level3 issue there.<br>
<br>
I think the route has to do with Tustin > LA, every trace that
has replied to this thread has been through an alternate route.<br>
<br>
Thanks.<br>
<pre><font color="#000000" face="terminal" size="1">
---- 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
</font></pre>
<br>
<pre><font color="#000000" face="terminal" size="1">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
</font></pre>
<div class="moz-cite-prefix">On 3/11/2014 9:41 AM, Jeremy Chadwick
wrote:<br>
</div>
<blockquote cite="mid:20140311164133.GA50925@icarus.home.lan"
type="cite">
<pre wrap="">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:
<a class="moz-txt-link-freetext" href="http://lookingglass.level3.net/">http://lookingglass.level3.net/</a>
</pre>
</blockquote>
<br>
</body>
</html>