BGP Tools

BGP Community Parser

Paste community values in standard, extended, or large format and TelcoAIO will decode RFC-known and carrier-specific meanings.

Batch mode accepts spaces or line breaks. Example: 65535:65281 3356:666 rt:64512:100 3356:201:300

This is meant for the operational moment when a route has communities attached and you need to understand whether they signal blackholing, local preference, location, export control, VPN context, or an operator-specific routing instruction.

Why Community Decoding Matters

BGP communities often carry the most important intent on a route, but they are also easy to misread when formats are mixed together. Standard communities, route targets, large communities, and provider-specific conventions can all appear in the same workflow. A quick decode helps you decide whether a route is just informational, whether it is meant to influence policy, or whether it belongs to a service context such as VPN transport.

How To Interpret The Results

The parser can tell you what type a value appears to be and whether it matches a known public reference. That means some results are precise, such as RFC-defined values, while others are best-effort matches based on public operator documentation. When the tool cannot map a value to a known meaning, that is often a sign that the community is private, locally defined, or documented only inside an operator network.

Common Mistakes

Do not assume that every ASN:value pair is globally meaningful outside the operator that defined it. Community conventions vary widely, and a value reused by another network can mean something completely different. This page is most useful as a decoding and triage aid before you check the provider's own routing policy or peering guide.