Yes. In the fallout from the Cloudflare attack of last week it was announced that several IXs were going to stop advertising the address space of their peering lan, which properly does not need to be advertised anyway. Yes, that will cause some minor problems for those who work for and with the companies that peer there, but they are *clients*, and should be able to have other similar arrangements made for them. Cheers, -- jra ----- Original Message -----
From: "Yang Yu" <yang.yu.list@gmail.com> To: kemp@network-services.uoregon.edu Cc: "NANOG list" <nanog@nanog.org> Sent: Wednesday, April 3, 2013 7:20:44 PM Subject: Re: route for linx.net in Level3? I noticed it too this morning from a AS3549 customer. Level 3 LG shows no route for 195.66.232.0/22 on North American sites.
On Wed, Apr 3, 2013 at 6:52 PM, John Kemp <kemp@network-services.uoregon.edu> wrote:
Having trouble reaching route-views.linx.routeviews.org from AS3582.
I'm assuming that some folks stopped carrying this particular linx.net address prefix as of this morning. ?!?
$ whois -h whois.cymru.com " -v 195.66.241.146" AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name 5459 | 195.66.241.146 | 195.66.240.0/22 | GB | ripencc | 1997-12-01 | LINX-AS London Internet Exchange Ltd.
$ dig +short 146.241.66.195.peer.asn.cymru.com TXT "1299 2914 3257 10310 | 195.66.240.0/22 | GB | ripencc | 1997-12-01"
-- John Kemp (kemp@routeviews.org) RouteViews Engineer NOC: noc@routeviews.org MAIL: help@routeviews.org WWW: http://www.routeviews.org
-- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274