Skip to content
AdminKit

BGP community

What is BGP community?

A BGP community, defined in RFC 1997, is an optional tag a router attaches to a BGP announcement so neighboring networks can apply routing policy -- prefer, de-prioritize, or null-route it -- without a bespoke filter for every case. AdminKit's WHOIS tool looks up the ASN behind a route before checking its community values.

By AdminKit team, Netbase JSC · Updated

A BGP community, defined in RFC 1997 (tracked on the IETF Datatracker), is an optional 32-bit value a router can attach to a BGP announcement as a tag, conventionally written AS:VALUE, that signals routing policy intent to the networks receiving that announcement — prefer this route, de-prioritize it, don’t re-announce it further, or route it to a null interface — without the two networks needing to coordinate a bespoke prefix-list filter for every case. A community is carried as an optional transitive path attribute, meaning it can propagate across multiple networks along with the route itself, so an operator several hops away from where a community was set can still match on it and act accordingly, provided every network in between preserves it. Some values are well-known rather than set by one operator: FRRouting’s BGP documentation, for instance, lists NO_EXPORT (0xFFFFFF01), which marks a route that must not be advertised outside a BGP confederation boundary. Because the original 32-bit format splits evenly into two 16-bit halves, it ran out of room to name autonomous systems once 32-bit ASNs became common, which RFC 8092 addresses with Large BGP Communities: a 96-bit value split into three 32-bit fields, large enough to hold a full 32-bit ASN. Communities are also the mechanism behind remote-triggered black holing, a DDoS mitigation technique NIST SP 800-189 documents, where a network operator tags a route with a community its upstream has published specifically to mean “drop all traffic to this prefix,” letting a DDoS target signal its own upstream to null-route an attack without a phone call.

What a BGP community can signal:

  • Routing preference: prefer, de-prioritize, or don’t re-announce a given route.
  • Black-holing: tag traffic to a prefix for an upstream to drop during an attack.
  • Scale: RFC 8092’s Large Communities extend the original 32-bit format to carry a full 32-bit ASN.

BGP community is part of AdminKit’s IP & network cluster; the full AdminKit glossary lists other related terms.

Frequently asked questions

What can a BGP community signal to a neighboring network?

Routing policy intent -- prefer a route, de-prioritize it, don't re-announce it further, or route it to a null interface -- without a bespoke prefix-list filter for every case.

Does a BGP community always stay within the network that set it?

No -- it's carried as an optional transitive path attribute, so it can propagate across multiple networks along with the route itself, as long as each network in between preserves it.

Why was the original 32-bit BGP community format extended?

Because it splits evenly into two 16-bit halves, it ran out of room to name autonomous systems once 32-bit ASNs became common, which RFC 8092's Large BGP Communities address with a 96-bit value.

What is remote-triggered black holing?

A mechanism where a network operator tags a route with a community its upstream has published specifically to mean 'drop all traffic to this prefix,' letting a DDoS target signal its upstream to null-route an attack without a phone call.