Registry Working Group

[Ryan Harden <>]

All of my prefixes are just marked as “Transit Only”, which is expected as I 
don’t have a direct peering with Google (though we apparently qualify!).

I have everything in my IRR except an export filter which I intend to add 
soon-ish.

/Ryan

Ryan Harden
Research and Advanced Networking Architect
University of Chicago - ASN160
P: 773.834.5441




> On Aug 22, 2019, at 4:49 PM, Jeff Bartig <> wrote:
> 
> You may want to check again.  Google deployed some new software this week.  
> I'm now seeing most prefixes flagged as "Invalid IRR".  60% of these 
> prefixes have valid IRR, but I2PX/AS11164 hasn't published an AS-SET for 
> Google to use.
> 
> For those networks that have direct peering with Google, their ISP portal 
> is at:  https://isp.google.com/bgp/
> 
> Jeff
> 
> Bill Owens wrote on 8/15/19 8:05 PM:
>> I happened to check earlier today and there are no IRR errors on our 
>> routes, even though we know we still have some bad or missing records. We 
>> divided up the 29 peers between the three of us engineers to take care of 
>> and *some* folks are finished with their lists, but others aren’t ;)
>> 
>> Bill.
>> 
>> From:  <> on 
>> behalf of Jeff Bartig <>
>> Sent: Thursday, August 15, 2019 7:37 PM
>> To: ; Michael H Lambert
>> Subject: Re: [WG-IRR] Google IRR based route filtering public announcements
>> 
>> When I visit this their ISP Portal and login as AS11164 (I2PX), it does 
>> show me a list of all of the prefixes they receive from AS11164, but 
>> currently none of them are marked as having any IRR issues.  If you click 
>> on "filter by problem", there is a choice of "Invalid IRR", but it 
>> produces no results.  Does anyone else that has direct peering with Google 
>> see any of your prefixes flagged as Invalid IRR?
>> 
>> Jeff
>> 
> --
> Jeff Bartig
> Interconnection Architect
> Internet2  AS11164 / AS11537
> +1-608-616-9908
>

Attachment: signature.asc
Description: Message signed with OpenPGP