BGP Large Communities - AS47536

Format: All communities use 47536:TYPE:ASN - Large communities only (RFC 8092)
Note: Standard communities are accepted for RTBH only (65535:666 and 47536:666)
Current network details: See PeeringDB and BGP.tools

Informational Communities

These are automatically added by AS47536 to routes we advertise to you:

Community Description
47536:150:0Transit routes (general)
47536:150:ASNTransit routes learned from specific transit ASN
47536:300:0Public peering routes (IXP, general)
47536:300:ASNPublic peering routes from specific IXP RS ASN
47536:400:0Private peering routes (PNI, general)
47536:400:ASNPrivate peering routes from specific peer ASN
47536:500:0Customer routes (general)
47536:500:ASNCustomer routes from specific customer ASN
47536:47536:0Routes originated by AS47536

Action Communities

Set these communities on your announcements to control how we propagate your routes:

Per-Transit Controls

Supported transit ASNs: 49600 (NEAR IP), 5405 (Inter.link), 34927 (iFog), 6762 (TIS Seabone), 34549 (meerfarbig), 50869 (IPTP)

Community Action
47536:800:ASNDo not announce to specific transit provider
47536:801:ASNPrepend AS47536 1x to specific transit
47536:802:ASNPrepend AS47536 2x to specific transit
47536:803:ASNPrepend AS47536 3x to specific transit
47536:805:ASNAnnounce ONLY to specific transit (exclusive)

Per-IXP Controls

Supported IXP route server ASNs: 47498 (FogIXP), 61190 (ANIX), 202409 (LocIX), 31142 (KleyReX), 41441 (Speed-IX)

Community Action
47536:810:ASNDo not announce to specific IXP (via route server)
47536:811:ASNPrepend AS47536 1x to specific IXP
47536:812:ASNPrepend AS47536 2x to specific IXP
47536:813:ASNPrepend AS47536 3x to specific IXP
47536:815:ASNAnnounce ONLY to specific IXP (exclusive)

General Controls

Community Action
47536:890:0Do not announce to ANY transit provider
47536:891:0Do not announce to ANY IXP
47536:892:0Prepend AS47536 1x to ALL IXPs
47536:893:0Prepend AS47536 2x to ALL IXPs
47536:894:0Prepend AS47536 3x to ALL IXPs
47536:895:0Prepend AS47536 1x to ALL transits
47536:896:0Prepend AS47536 2x to ALL transits
47536:897:0Prepend AS47536 3x to ALL transits

Special Communities

Community Action
47536:666:0RTBH - Trigger blackhole (prefix must be /32 or /128)
65535:666RTBH - Standard community alternative
47536:666RTBH - Standard community alternative
65535:0Graceful Shutdown (RFC 8326)

Important Notes

Examples

Common traffic engineering scenarios using community combinations:

Example 1: Primary/Backup Transit Setup

Goal: Use NEAR IP as primary, Inter.link as backup
Communities: 47536:803:5405
Result: Route prepended 3x to Inter.link (AS5405), making NEAR IP (AS49600) preferred

Example 2: Avoid Specific Transit

Goal: Do not use iFog transit
Communities: 47536:800:34927
Result: Route not announced to iFog (AS34927), uses other available transits

Example 3: IXP-Only Routing

Goal: Route only via IXPs, no transit usage
Communities: 47536:890:0
Result: Route announced to all IXP route servers, but not to any transit provider

Example 4: Single Transit Exclusive

Goal: Force all traffic through TIS Seabone only
Communities: 47536:805:6762
Result: Route ONLY announced to TIS Seabone (AS6762), not to any other transit or IXP

Example 5: Complex Multi-Transit Engineering

Goal: Primary: NEAR IP, Secondary: meerfarbig (prepend 2x), Avoid: iFog and IPTP
Communities: 47536:802:34549 47536:800:34927 47536:800:50869
Result:

Example 6: RTBH (Remote Triggered Black Hole)

Goal: Black hole traffic to specific /32 under DDoS attack
Communities: 47536:666:0 or 65535:666
Requirements: Prefix must be /32 (IPv4) or /128 (IPv6)
Result: Traffic to prefix is dropped at all upstreams supporting RTBH

AS47536 - PathConnect GmbH
Last updated: December 2024