We offer BGP communities to IP transit customers, currently only in our US network (AS60011). These can be used to filter which routes from us you use, or to filter what other networks we will advertise your routes to.
Please note that these are all BGP Large Communities, as defined in RFC8092.
Select a network
We will set these on routes we send to you.
|0||peer type||Route learned from peer with peer type|
|1||site ID||Route learned at site ID|
|2||peer ASN||Route learned from network peer ASN|
|3||IXP ID||Route learned at IXP ID|
You can use these to control who we send your routes to.
These communities control how we export routes throughout our entire network:
|1000||1||Global prepend once|
|1000||2||Global prepend twice|
|1000||3||Global prepend thrice|
These communities control how we export routes to specifix IXPs:
|2000||IXP ID||No-export to IXP id|
|2001||IXP ID||Prepend once to IXP id|
|2002||IXP ID||Prepend twice to IXP id|
|2003||IXP ID||Prepend thrice to IXP id|
|2999||IXP ID||Override no-export to IXP id|
These communities control how we export routes to specifix ASes:
|3000||ASN||No-export to AS ASN|
|3001||ASN||Prepend once to AS ASN|
|3002||ASN||Prepend twice to AS ASN|
|3003||ASN||Prepend thrice to AS ASN|
|3999||ASN||Override no-export to AS ASN|
These communities control how we export routes from specific sites:
|4000||site ID||No-export from site site ID|
|4001||site ID||Prepend once from site site ID|
|4002||site ID||Prepend twice from site site ID|
|4003||site ID||Prepend thrice from site site ID|
|4999||site ID||Override no-export from site site ID|
These communities control how we export routes based on peer type:
|5000||type ID||No-export to peers with type ID|
|5001||type ID||Prepend once to peers with type ID|
|5002||type ID||Prepend twice to peers with type ID|
|5003||type ID||Prepend thrice to peers with type ID|
|5999||type ID||Override no-export to peers with type ID|
This can only be used on /32 routes for IPv4, or /128 routes for IPv6. We will discard all traffic to blackholed prefixes, and will pass the advertisement to do so onto our upstreams.
|1000||666||Blackhole all traffic to the address|
For communities that include a site ID, you can use the following:
|100||Hurricane Electric Fremont 2|
Internet exchange IDsUnless otherwise noted, we use use IXP IDs from PeeringDB - for example, LINX LON1 has the ID 18, as can be seen in the PeeringDB URL.
For communities that are based on peer type, we use the following identifiers:
|800||Our private peers|
|600||Our transit providers|