[176411] in North American Network Operators' Group
Re: Anyone else having trouble reaching thepiratebay.se? AS39138
daemon@ATHENA.MIT.EDU (Phil Bedard)
Thu Nov 27 14:07:01 2014
X-Original-To: nanog@nanog.org
Date: Thu, 27 Nov 2014 14:06:52 -0500
From: Phil Bedard <bedard.phil@gmail.com>
To: Javier J <javier@advancedmachines.us>,
Courtney Smith <courtneysmith@comcast.net>
In-Reply-To: <CA+M5dWaKXfgnGVY7N3fMNei7UTR2bcO3xYCD0_RG-bsj_pHdag@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
In the post you quoted it says: =20
"In my last post I pointed out the do not announce to peers
community AS5580 was sending to Cogent, Level3 and who knows who else. So
any ASN that is not a customer of Cogent or Level3 wont learn the 5580 path
from them."
Verizon, ATT, and the rest of those networks are Tier-1 networks meaning=20
if 5580 was tagging the route with do-not-advertise to their transit=20
providers (Level3 & Cogent) the other Tier-1s wouldn't have another route=20
to it. Looking at routing updates there were a lot of them yesterday for=20
that prefix, for whatever reason. The lack of reachability was completely=20
due to Atrato, had nothing to do with the ISPs in the US. =20
It was reachable for me yesterday on our network, but we peer directly=20
with Atrato.
It's possible they did it to stop a DDoS, some other kind of attack, or=20
any number of reasons. =20
Phil=20
On 11/27/14, 2:47 PM, "Javier J" <javier@advancedmachines.us> wrote:
>Looks like its working now (on FIOS anyway)
>
>Curious to know why the major networks stopped seeing it yesterday as=20
>well.
>
>On Thu, Nov 27, 2014 at 12:45 AM, Courtney Smith=20
><courtneysmith@comcast.net>
>wrote:
>
>>
>> > No problem here in Los Angeles either, but seeing a lone route through
>> Atrato only.
>> >
>> > flags destination gateway lpref med aspath origin
>> > *> 194.71.107.0/24 <> 100 0 3491 5580 39138 22351=20
>>2.207
>> 51040 i
>> > * 194.71.107.0/24 <> 100 0 174 5580 39138 22351
>> 2.207 51040 i
>> >
>> >
>> > On 11/27/2014 =E5=8D=88=E5=89=8D 11:24, Tony Wicks wrote:
>> >>
>> >> No problem here in New Zealand
>> >>
>> >> tonyw@vrhost1-w> show route 194.71.107.0/24
>> >>
>> >> icore1-w.inet.0: 519451 destinations, 525214 routes (519437 active,=20
>>14
>> >> holddown, 0 hidden)
>> >> + =3D Active Route, - =3D Last Active, * =3D Both
>> >>
>> >> 194.71.107.0/24 *[BGP/170] 10:25:44, MED 0, localpref 90
>> >> AS path: 4826 5580 39138 22351 131279 51040 I,
>> >> validation-state: unverified
>> >> > to 175.45.102.9 via ae1.526
>> >>
>>
>> Hopefully the body cones thru this time. The issue isn't city or=20
>>country
>> based. In my last post I pointed out the do not announce to peers
>> community AS5580 was sending to Cogent, Level3 and who knows who else. =20
>> So
>> any ASN that is not a customer of Cogent or Level3 wont learn the 5580=20
>>path
>> from them.
>>
>> When I checked a few hours ago, Comcast, Centurylink, AT&T, TATA, and
>> possibly Sprint were not seeing the /24 based on their public looking
>> glasses or route servers. Have not had time to run bgplay to see if
>> routeviews data shows how they previously saw the /24 in past 30 days.
>> Finding the ASN(s) they used to see from would shed light on why they
>> stopped seeing. Checking bgplay and contacting AS51040 to reach out to
>> their upstreams is my suggestion.
