BGP communities

Members use BGP communities to limit which peers receive a route, to prepend, to blackhole and to signal graceful shutdown. Informational communities record the RPKI and IRR state of each route. Both route servers run as AS9420 and honour the same communities on IPv4 and IPv6.

Published values

BGP communities with published values
CommunityMeaningSet by
9420:1000:1RPKI validRoute servers
9420:1000:2RPKI not foundRoute servers
9420:1001:1IRR validRoute servers
9420:1001:2IRR not checkedRoute servers
9420:1101:13Rejected, RPKI-invalidRoute servers
65535:666Blackhole request (RFC 7999)Member
65535:0Graceful shutdown (RFC 8326)Member

Version 1.1, published 1 October 2026.

Export control

By default the route servers announce your routes to every peer. Control communities let you leave out specific peers, or announce to selected peers only.

Prepending

You can ask the route servers to prepend your ASN towards all peers or towards one peer.

Blackholing and maintenance

Blackholing uses the well-known BLACKHOLE community 65535:666 (RFC 7999) on one address, a /32 for IPv4 or a /128 for IPv6, inside a prefix that your IRR data covers. Your IRR data must be current. The route servers mark a blackhole route NO_EXPORT, so that it stays inside the exchange, and each member decides in its own router whether to act on it. Graceful shutdown (RFC 8326) lowers the preference of your routes before planned maintenance.

Standard and large communities

Standard communities (RFC 1997) can only target peers with 16-bit ASNs. Large communities (RFC 8092) work for every peer.

Informational communities

Accepted routes carry their RPKI and IRR state. Rejected routes carry the reason and stay visible in the looking glass. The values that are published are in the table above. The other values are in the welcome guide sent to each member. For the meaning of a tag you see in the looking glass, email noc@maharlikaix.ph.

Control community values

The full list of control community values is in the welcome guide sent to each member. If you need another copy, email the peering team.