<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
2.|-- cr2.la2ca.ip.att.net 0.0% 1000 13.2 16.2 9.6
126.4 15.6<br>
3.|-- ggr2.la2ca.ip.att.net 0.0% 1000 9.7 15.7 8.6
144.1 16.9<br>
4.|-- 192.205.37.146 0.0% 1000 10.9 15.8 10.6
149.3 16.8<br>
5.|-- vl-3508-ve-122.ebr1.tusti 0.0% 1000 9.9 14.3 9.6
120.3 15.4<br>
6.|-- ae-6-6.ebr1.losangeles1.l 0.0% 1000 13.6 18.7 13.5
132.4 16.2<br>
7.|-- ae-81-81.csw3.losangeles1 0.0% 1000 12.6 17.2 12.3
147.4 16.5<br>
8.|-- ae-3-80.edge3.losangeles1 7.3% 1000 12.5 16.7 12.3
140.6 15.8<br>
9.|-- b.resolvers.level3.net 8.0% 1000 30.8 33.4 16.4
161.3 16.6<br>
<br>
2.|-- ae7.cr1.lax112.us.above.n 0.1% 1000 2.9 5.6 2.5
69.4 7.5<br>
3.|-- ae8.mpr1.lax12.us.above.n 21.7% 1000 2.7 3.2 2.4
63.9 4.7<br>
4.|-- ae7.edge2.LosAngles.Level 4.9% 1000 2.7 3.4 2.5
85.7 6.3<br>
5.|-- ae-1-60.edge3.LosAngeles1 6.1% 1000 3.4 2.8 2.5
21.9 1.9<br>
6.|-- b.resolvers.Level3.net 9.3% 1000 18.3 19.7 10.7
24.9 1.7<br>
<br>
<br>
<br>
problem is now gone..<br>
<br>
2.|-- cr2.la2ca.ip.att.net 0.0% 50 11.8 11.6 9.7
13.6 0.9<br>
3.|-- ggr2.la2ca.ip.att.net 0.0% 50 10.0 10.8 8.7
12.7 1.0<br>
4.|-- 192.205.37.146 0.0% 50 10.7 12.1 10.7
72.0 8.6<br>
5.|-- vl-3508-ve-122.ebr1.tusti 0.0% 50 9.9 9.9 9.7
11.8 0.3<br>
6.|-- ae-6-6.ebr1.losangeles1.l 0.0% 50 13.6 13.8 13.5
15.7 0.3<br>
7.|-- ae-81-81.csw3.losangeles1 0.0% 50 14.6 12.8 12.4
20.2 1.1<br>
8.|-- ae-3-80.edge3.losangeles1 0.0% 50 12.3 12.8 12.3
29.5 2.4<br>
9.|-- b.resolvers.level3.net 0.0% 50 12.0 18.7 11.7
29.4 5.8<br>
<br>
<div class="moz-cite-prefix">On 3/11/2014 10:28 AM, Tri Tran wrote:<br>
</div>
<blockquote cite="mid:531F47B1.2010600@cox.net" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<div class="moz-cite-prefix"><font face="Calibri">We couldn't ping
one IP in Tustin from the outside</font> (was able to ping
from same network) from 6:45am- 8:05am PST.<br>
Problem went away around 8:15 AM PST.<br>
Weird that only one IP was affected. <br>
<pre class="moz-signature" cols="72">--
Tri Tran</pre>
On 3/11/2014 10:15 AM, Jeremy Chadwick wrote:<br>
</div>
<blockquote cite="mid:20140311171557.GA51307@icarus.home.lan"
type="cite">
<pre wrap="">Your 1st traceroute shows loss happening within the Los Angeles region
possibly within Level3 (hop #8 from the look of it, and it looks like
multipathing is involved). Because traceroutes going only one direction
are provided (due to the destination you chose and the nature of
asymmetric routing), only half of the picture is shown, which is why I
say "possibly".
Your 2nd traceroute shows two things;
- Loss showing up starting at hop #3 (possibly within Zayo/Abovenet
space, again "possibly", re: asymmetric routing)
- Loss showing up at hop #8 (could be an effect of something happening
earlier in the path)
For reference, here are your traceroutes:
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://puck.nether.net/pipermail/outages/2014-March/006787.html">https://puck.nether.net/pipermail/outages/2014-March/006787.html</a>
So when you say "I think it's a problem with Tustin > LA", the 2nd
traceroute you provided doesn't seem to support that theory, nor the
statement "I am unable to reproduce it to any other network".
Do you have any other tools available to you, like mtr? mtr won't
narrow down where the issue is happening, but would make it more clear
as to where the issue is happening, especially if you let it run for a
while (say 10 minutes or so) from both places (you didn't provide source
IPs for either traceroute, so that doesn't help either).
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Outages mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Outages@outages.org">Outages@outages.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/outages">https://puck.nether.net/mailman/listinfo/outages</a>
</pre>
</blockquote>
<br>
</body>
</html>