[outages] AoL / XO services issues?

Wed May 11 16:38:34 EDT 2011

Are all the sources complaining of the issue on the same IP block? Traces
from the XO core in Dallas (via
http://xostats.xo.com/cgi-bin/xostats/diagtool-pub) show this going through
fine -- and they traverse the router you're stopping at:

 traceroute 205.188.251.44

 Type escape sequence to abort.
 Tracing the route to sbucp-d1-vip.blue.aol.com (205.188.251.44)

   1 65.106.2.49.ptr.us.xo.net (65.106.2.49) 4 msec 4 msec 0 msec
   2 ge11-1-0d0.mcr1.dallas-tx.us.xo.net (216.156.10.97) 16 msec 0 msec 0
msec
   3 vb1300.rar3.dallas-tx.us.xo.net (216.156.0.81) 0 msec 0 msec 4 msec
   4 207.88.12.146.ptr.us.xo.net (207.88.12.146) 0 msec 4 msec 4 msec <==
   5 206.111.5.22.ptr.us.xo.net (206.111.5.22) 0 msec 0 msec 4 msec
   6 bb1-dls-s0-0-0.atdn.net (66.185.133.96) [MPLS: Label 300304 Exp 0] 0
msec 0 msec 4 msec
   7 bb1-atm-S1-2-0.atdn.net (66.185.152.153) [MPLS: Label 300400 Exp 0] 24
msec 24 msec 24 msec

and on ward to the destination...could be a reachability/acl issue blocking
traffic back to you on 207.88.12.146.

I can reach the host fine as well from my network, but my traces do not go
through XO.

cheers

Tom

On Wed, May 11, 2011 at 4:13 PM, Chris Boyd <cboyd at gizmopartners.com> wrote:

> We're seeing an few tickets and calls for issues with AoL based services.
>
> Specifically, AIM logins are timing out when trying to get to
> slogin.oscar.aol.com or login.oscar.aol.com.  We see these resolving to
> 205.188.251.44 and 205.188.251.43 respectively, and traceroutes die
> somewhere in XO Dallas (207.88.12.146).
>
> Also, www.engadget.com times out, again with the traceroutes dying in XO
> Dallas.
>
> We're seeing this across multiple providers in Central Texas since
> yesterday afternoon.
>
> --Chris
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20110511/0bd17fa0/attachment.htm>