Frequently Asked Questions

Which IRRs can I use?

We currently use: 

  • ALTDB
  • APNIC
  • ARIN
  • BBOI
  • BELL Canada
  • CANARIE
  • EASYNET
  • HOST
  • JPIRR
  • Level3
  • LACNIC
  • NESTEGG
  • NTT
  • OPENFACE
  • OTTIX
  • PANIX
  • REACH
  • RADB
  • RGNET
  • RIPE
  • RISQ
  • ROGERS,
  • TC
     

 

If your IRR isn’t listed, let us know at noc@google.com and we will review. If you also use an AS-SET, you must update the IRR record in PeeringDB with your AS-SET.

 

Do you use AS-SETs to compile the filters?

Yes, update yours at your PeeringDB record.

 

I modified some IRR objects. How long does it take Google to process it?

We’re still working on timelines to update IRR data and router configurations. We automatically process new data every day. Allow 48 hours for our systems to update. If you encounter problems or have an emergency let us know.


 
I peer with Google with a PNI and/or IXP. Do I need IRR objects for my ASN and prefixes?

Yes, IRR objects are required.
 

 

I do not peer with Google. Do I need to have IRR objects for my ASN and prefixes?

We recommend that you keep your IRR data up to date to avoid traffic shifts, as we might not accept all of your prefixes. We’ll apply filters to your transit provider that might be peering with us. If you or your transit provider don’t create IRR data, we’ll filter your prefixes.

   

My IRR is updated. Do I need something else?

If you also use an AS-SET, update the IRR record in PeeringDB with your AS-SET.

 

Does this apply to GGC?

No, this is only for peering.

 

Where can I find if my prefixes are valid or invalid?

You can check the status of your prefixes at the ISP Portal under Monitoring -> Routing -> BGP. Information on how to use this tool is on the Interconnect Help ->; BGP page.

You can use also these external tools to check the general validity of your prefixes:

 

Where can I find more information about IRR and this project?

You can find documentation, IRR resources and more information at the ISP Portal under Support -> Help ->Interconnection -> Peering: Route Filtering 

 

Does Google apply inbound route filters to the BGP session with their peers?

Yes. To build these filters we’ll use your ASN data on the IRR system. To avoid routing issues, keep your Maintainer, ASN, AS-SET, and Route / Route6 objects up to date.

 

Should I expect traffic shifts after Google starts filtering?

If your prefix and ASN data are updated in the IRR and you’re announcing accordingly you shouldn’t see any traffic shift. If your prefixes are being marked as invalid you might see some shifts.

 

My traffic shifted from peering to transit, is it related to this project?

Possibly. We recommend that you check the validity of your prefixes at the ISP Portal under under Monitoring -> Routing -> BGP.

If you have invalid prefixes resolve those issues before contacting us. If all your prefixes are valid contact us at noc@google.com.

 

I have the same prefixes in various IRRs. Which IRR would Google use?

In these cases we will use the record with the most recent timestamp.

 

Where do I find more information?

To learn more about this process visit Interconnect Help and see the Peering: Route Filtering topic.

Was this helpful?
How can we improve it?
Search
Clear search
Close search
Google apps
Main menu
Search Help Center
false