[outages] AT&T Apparently Blocking ooVoo -- WAS: Re: ooVoo WebSite Outage?

[Frank Bulk]

Let's move this to outages-discussion.

Jim: I would suggest having your ISP send traffic for 63.111.29.0/24 to one
of their other upstream providers, to route around the issue, and then open
a ticket with AT&T.

Frank

-----Original Message-----
From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
Behalf Of Network Operations
Sent: Thursday, November 15, 2012 5:15 PM
To: outages
Subject: Re: [outages] AT&T Apparently Blocking ooVoo -- WAS: Re: ooVoo
WebSite Outage?

I do not have AT&T as an ISP.  However, my ISP does have them as one of
their upstream providers.  It appears BGP is trying to route packets
destined for 63.111.29.0/24 via the AT&T upstream and I can see it failing
as soon as it hits AT&T's network.

Jim

On Nov 15, 2012, at 5:41 PM, Chris Adams wrote:

> Once upon a time, Seth Mattinen <sethm at rollernet.us> said:
>> I'm curious to know if they're pushing a blocking ACL to MIS with
>> managed (AT&T provided) routers or further up from that, which would
>> mean that customers with their own router wouldn't be affected.
> 
> It appears to be dropped in their entire network.  I tried it from
> route-server.ip.att.net (telnet); I can trace to 63.111.29.131 and
> 63.111.29.133 (at least into AS 11486), but trace to 63.111.29.132 dies
> after 1 hop.
> -- 
> Chris Adams <cmadams at hiwaay.net>
> Systems and Network Administrator - HiWAAY Internet Services
> I don't speak for anybody but myself - that's enough trouble.
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages


_______________________________________________
Outages mailing list
Outages at outages.org
https://puck.nether.net/mailman/listinfo/outages