Are all the sources complaining of the issue on the same IP block? Traces from the XO core in Dallas (via <a href="http://xostats.xo.com/cgi-bin/xostats/diagtool-pub">http://xostats.xo.com/cgi-bin/xostats/diagtool-pub</a>) show this going through fine -- and they traverse the router you're stopping at:<div>
<br></div><div><div> traceroute 205.188.251.44 </div><div> </div><div> Type escape sequence to abort.</div><div> Tracing the route to <a href="http://sbucp-d1-vip.blue.aol.com">sbucp-d1-vip.blue.aol.com</a> (205.188.251.44)</div>
<div> </div><div> 1 <a href="http://65.106.2.49.ptr.us.xo.net">65.106.2.49.ptr.us.xo.net</a> (65.106.2.49) 4 msec 4 msec 0 msec</div><div> 2 <a href="http://ge11-1-0d0.mcr1.dallas-tx.us.xo.net">ge11-1-0d0.mcr1.dallas-tx.us.xo.net</a> (216.156.10.97) 16 msec 0 msec 0 msec</div>
<div> 3 <a href="http://vb1300.rar3.dallas-tx.us.xo.net">vb1300.rar3.dallas-tx.us.xo.net</a> (216.156.0.81) 0 msec 0 msec 4 msec</div><div> 4 <a href="http://207.88.12.146.ptr.us.xo.net">207.88.12.146.ptr.us.xo.net</a> (207.88.12.146) 0 msec 4 msec 4 msec <==</div>
<div> 5 <a href="http://206.111.5.22.ptr.us.xo.net">206.111.5.22.ptr.us.xo.net</a> (206.111.5.22) 0 msec 0 msec 4 msec</div><div> 6 <a href="http://bb1-dls-s0-0-0.atdn.net">bb1-dls-s0-0-0.atdn.net</a> (66.185.133.96) [MPLS: Label 300304 Exp 0] 0 msec 0 msec 4 msec</div>
<div> 7 <a href="http://bb1-atm-S1-2-0.atdn.net">bb1-atm-S1-2-0.atdn.net</a> (66.185.152.153) [MPLS: Label 300400 Exp 0] 24 msec 24 msec 24 msec</div><div><br></div><div>and on ward to the destination...could be a reachability/acl issue blocking traffic back to you on 207.88.12.146.</div>
<div><br></div><div>I can reach the host fine as well from my network, but my traces do not go through XO.</div><div><br></div><div>cheers</div><div><br></div><div>Tom</div><br><div class="gmail_quote">On Wed, May 11, 2011 at 4:13 PM, Chris Boyd <span dir="ltr"><<a href="mailto:cboyd@gizmopartners.com">cboyd@gizmopartners.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">We're seeing an few tickets and calls for issues with AoL based services.<br>
<br>
Specifically, AIM logins are timing out when trying to get to <a href="http://slogin.oscar.aol.com" target="_blank">slogin.oscar.aol.com</a> or <a href="http://login.oscar.aol.com" target="_blank">login.oscar.aol.com</a>. We see these resolving to 205.188.251.44 and 205.188.251.43 respectively, and traceroutes die somewhere in XO Dallas <a href="tel:%28207.88.12.146" value="+12078812146">(207.88.12.146</a>).<br>
<br>
Also, <a href="http://www.engadget.com" target="_blank">www.engadget.com</a> times out, again with the traceroutes dying in XO Dallas.<br>
<br>
We're seeing this across multiple providers in Central Texas since yesterday afternoon.<br>
<br>
--Chris<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>