And because they're continuing to announce the /20, we run into their blackhole unless we manually filter that /20. This is going to become unworkable in short order once a bigger chunk of the internet starts doing this. /kc On Fri, Feb 10, 2017 at 03:03:11PM -0500, Christopher Morrow said:
On Fri, Feb 10, 2017 at 1:39 PM, Mike Hammett <nanog@ics-il.net> wrote:
Have we determined that this is intentional vs. some screw up?
if you look at the cogent LG it's pretty clear that the announce reachability for the /20 that includes the tpb /32.. and that the /32 is particularly routed elsewhere, and that the 'elsewhere' is coming form a bgp speaker who's DNS says something along the lines of: "blackhole"...
so... err, either someone fat-fingered OR intentionally entered a /32 into the config management system :(
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
Midwest-IX http://www.midwest-ix.com
----- Original Message -----
From: "Brielle Bruns" <bruns@2mbit.com> To: nanog@nanog.org Sent: Friday, February 10, 2017 12:28:53 PM Subject: Re: backbones filtering unsanctioned sites
On 2/9/17 9:18 PM, Ken Chase wrote:
https://torrentfreak.com/internet-backbone-provider- cogent-blocks-pirate-bay-and-other-pirate-sites-170209/
/kc
Funny. Someone else got back:
"Abuse cannot not provide you a list of websites that may be encountering reduced visibility via Cogent"
I almost wish I had a Cogent circuit just to bring this up with an account rep. Almost.
I'd very much so view this as a contractual violation on Cogent's part.
Cogent keeps contacting me every year wanting to sell me service. This will be a good one to bring up when they call me next time.
-- Brielle Bruns The Summit Open Source Development Group http://www.sosdg.org / http://www.ahbl.org
-- Ken Chase - math@sizone.org Guelph/Toronto Canada Heavy Computing - Clued bandwidth, colocation and managed linux VPS @151 Front St. W.