--- title: "BGP Communities" description: "Every BGP community CubePath (AS26141) accepts on customer announcements: local preference, RTBH blackholing, DDoS scrubbing, no-export, selective export overrides, AS-path prepending and MED." category: "Deployment" language: en source: https://cubepath.com/docs/products/deployment/ip-transit-bgp-communities updated: 2026-11-17 --- # BGP Communities If you announce your own prefixes to CubePath (**AS26141**), over an [IP Transit](/docs/products/deployment/order-ip-transit) port or a [tunnel](/docs/products/security/tunnels), you can attach standard BGP communities in the form `26141:XXXXX` to control how we handle your route. Communities are processed in this order: 1. **Local preference** from customer action communities 2. **No-export** communities decide which providers must *not* receive the prefix 3. **Selective export** overrides force export despite a no-export tag 4. **Prepending** communities shape inbound traffic 5. **Blackhole** communities trigger RTBH if present > Note: By default, customer routes receive the highest local preference in our network (**200**), so they are preferred over transit, IXP or PNI routes. ## Network locations | Region | Location | Transits | IXPs | |--------|----------|----------|------| | Europe | Barcelona, Spain | Cogent, GTT, Telxius | DE-CIX Barcelona, DE-CIX Madrid | | Europe | Amsterdam, Netherlands | Cogent, GTT | Inter-IX, Speed-IX, Frys-IX, PiterIX-FRA, PiterIX-MSK, PiterIX-SPB | | North America | Houston, Texas | Lumen, Cogent, GTT | - | | North America | Miami, Florida | Lumen, Cogent, GTT | FL-IX | | North America | Ashburn, Virginia | Lumen, Cogent, GTT | CIX-NoVA | ## Local preference | Community | Effect | |-----------|--------| | `26141:8000` | Lower local-pref to 90 on all routers **outside** the continent where the prefix is received | | `26141:8090` | Lower local-pref to 90 on **all** routers, making the prefix a global backup | Use `26141:8000` on a backup site so only its own continent uses it, and `26141:8090` to make a session the last-resort path everywhere. ## Blackhole (RTBH) | Community | Effect | |-----------|--------| | `26141:666` | Blackhole internally and signal upstreams to blackhole the prefix | | `65535:666` | The RFC 7999 well-known blackhole community, also accepted | Blackhole announcements must be **/32** (IPv4) or **/128** (IPv6), and must be covered by a less-specific prefix you already announce. Propagated to Cogent (AS174), Lumen (AS3356), GTT (AS3257) and Telxius (AS12956). ## DDoS scrubbing | Community | Effect | |-----------|--------| | `26141:112` | Route the prefix through dedicated inline filtering appliances | The difference from blackholing is the whole point: **blackhole drops all traffic** and the IP goes dark, while **scrubbing filters attack traffic** and keeps delivering legitimate traffic, so the IP stays reachable. > Note: CubePath mitigates volumetric attacks locally with no community required. `26141:112` is for deeper inline inspection, and is available only on the **AntiDDoS Premium** plan. ## No multihoming By default your prefixes are announced from every CubePath site. These restrict that: | Community | Mode | Effect | |-----------|------|--------| | `26141:6888` | **Strict** | Announced only from the site you're connected to; no other site announces it anywhere | | `26141:6889` | **Relaxed** | Announced only from your site, but still internally reachable across CubePath | Strict is the one for data-residency or geographic compliance requirements. Relaxed keeps internal connectivity to other sites without external announcement. > Note: No-multihoming mode is configured at the service level: contact support to enable or change it. ## No-export | Community | Effect | |-----------|--------| | `26141:9000` | Do not export to **any** provider (transit, IXP or PNI) | | `26141:30000` | Do not export to any transit provider | | `26141:40000` | Do not export to any IXP | **By transit provider:** `30020` Lumen · `30030` Cogent · `30040` GTT · `30050` Telxius. **By IXP:** `40010` FL-IX · `40020` Inter-IX · `40030` Speed-IX · `40040` Frys-IX · `40050` PiterIX-FRA · `40060` PiterIX-MSK · `40070` PiterIX-SPB · `40080` DE-CIX Barcelona · `40090` DE-CIX Madrid · `40100` CIX-NoVA. **By continent:** `51000` Europe · `52000` North America. **By country/state:** `51010` Spain · `51020` Netherlands · `52010` Texas · `52020` Florida · `52030` Virginia. ## Selective export override These **override** a no-export tag, so you can suppress broadly and still allow one provider. They do nothing on their own. | Community | Effect | |-----------|--------| | `26141:9120` | Override no-export for all transit providers | | `26141:9110` | Override no-export for all IXPs | **Force export to a transit:** `9122` Lumen · `9123` Cogent · `9124` GTT · `9125` Telxius. **Force export to an IXP:** `9111` FL-IX · `9112` Inter-IX · `9113` Speed-IX · `9114` Frys-IX · `9115` PiterIX-FRA · `9116` PiterIX-MSK · `9117` PiterIX-SPB · `9118` DE-CIX Barcelona · `9119` DE-CIX Madrid. CIX-NoVA has no individual override: use `26141:9110`. ## AS-path prepending Prepending makes your path look longer so remote networks prefer another route. **The last digit is the number of prepends** (1, 2 or 3) throughout. | Scope | Communities | |-------|-------------| | **Everywhere** | `26141:9001` / `9002` / `9003` | | **By continent** | `51001-51003` Europe · `52001-52003` North America | | **By country/state** | `51011` Spain · `51021` Netherlands · `52011` Texas · `52021` Florida · `52031` Virginia | | **By transit** | `30021-30023` Lumen · `30031-30033` Cogent · `30041-30043` GTT · `30051-30053` Telxius | | **By IXP** | `40011-40013` FL-IX · `40021-40023` Inter-IX · `40031-40033` Speed-IX · `40041-40043` Frys-IX · `40051-40053` PiterIX-FRA · `40061-40063` PiterIX-MSK · `40071-40073` PiterIX-SPB · `40081-40083` DE-CIX Barcelona · `40091-40093` DE-CIX Madrid · `40101-40103` CIX-NoVA | ## MED CubePath **honours your MED and never modifies it** on inbound; it's preserved across our network. Lower MED is more preferred. Since customer routes carry local-pref 200 by default, MED is the tiebreaker between multiple paths from the same customer, which makes it the cleanest way to express "prefer Miami, fall back to Houston" when you're multi-homed to us at several sites. ## Worked examples | Goal | Communities | |------|-------------| | Announce **only** to Cogent | `26141:9000` (no export at all) + `26141:9123` (force Cogent) | | Announce everywhere **except** IXPs | `26141:40000` | | Keep the prefix off DE-CIX Madrid | `26141:40090` | | Backup site in Miami | `26141:8000` on the Miami session | | Blackhole a /32 under attack | `26141:666` on the /32 | | Make Europe prefer another provider | `26141:51002` (prepend 2x at EU sites) | ## Getting help Traffic engineering is easy to get subtly wrong, and a bad community combination is usually invisible from your side: the prefix simply stops appearing where you expected. If a change does not behave the way this page describes, open a support ticket with the prefix, the communities you attached and the session it was announced from, and we will look at what our routers actually received.