Customer routing controls for AS215828
Blackhole, prepending, local preference, export scope, protected transit, and maintenance communities for customers announcing prefixes to TMW Global Networks.
ASN
AS215828
AS-SET
AS-TMW
Well-known blackhole
65535:666
Route validation
IRR + RPKI
Community reference
A small control surface, documented clearly.
These communities are designed for production operations: route suppression during incidents, inbound steering, customer failover, and protected handoff behavior. Product contracts define which controls are enabled on each BGP session.
Blackhole and discard
Community
65535:666Name
RFC 7999 blackhole
Action
Discard traffic for the tagged /32 or /128 at the edge
Notes
Preferred standard blackhole signal. Prefix must be covered by an accepted customer route.
Community
215828:666Name
TMW blackhole alias
Action
Same discard action as RFC 7999
Notes
Accepted as an AS-specific alias for customers that cannot send well-known communities.
Prepending controls
Community
215828:101Name
Prepend once
Action
Prepend AS215828 one time toward upstreams and IX route servers
Notes
Used for mild inbound traffic steering.
Community
215828:102Name
Prepend twice
Action
Prepend AS215828 two times
Notes
Used when a route should remain backup but still reachable.
Community
215828:103Name
Prepend three times
Action
Prepend AS215828 three times
Notes
Strong inbound de-preference without withdrawing the route.
Local preference
Community
215828:70Name
Low local-pref
Action
Set customer route to backup preference inside AS215828
Notes
Good for standby circuits, maintenance, or overflow paths.
Community
215828:100Name
Standard local-pref
Action
Use normal customer route preference
Notes
Default if no local-pref community is sent.
Community
215828:120Name
High local-pref
Action
Prefer this customer ingress path inside AS215828
Notes
Requires prior approval when multiple customer sessions announce the same prefix.
Export scope
Community
65535:65281Name
NO_EXPORT
Action
Keep route inside AS215828 and directly connected peers that honor NO_EXPORT
Notes
Useful for internal testing or controlled maintenance announcements.
Community
215828:900Name
Do not announce to transit
Action
Advertise only to settlement-free peers and route servers
Notes
Use when a route should avoid paid transit export.
Community
215828:901Name
Do not announce to IX route servers
Action
Advertise to transit and bilateral peers only
Notes
Used for troubleshooting route-server path selection.
Customer controls
Community
215828:300Name
Protected transit
Action
Force route through TMW Shield mitigation policy
Notes
Enabled for DDoS Protected Transit and Remote Protection customers.
Community
215828:301Name
Clean-only handoff
Action
Forward post-filter traffic only to configured GRE/IPIP/native handoff
Notes
Used during emergency onboarding and asymmetric origin protection.
Community
215828:999Name
Customer maintenance
Action
Suppress automated alerts for a planned route change
Notes
Must include a maintenance ticket reference for NOC correlation.
Turn-up rules
Predictable behavior during incidents.
Community handling is deterministic. The NOC validates policy at session turn-up, and customer dashboards show received communities during route troubleshooting.
Communities are evaluated only on accepted customer routes after prefix ownership, IRR, and RPKI checks pass.
Blackhole routes must be more-specific host routes covered by an accepted aggregate and are never propagated as normal transit.
Conflicting communities are resolved by most restrictive action first: blackhole, suppress export, local-pref, then prepending.
Per-upstream export controls can be added during turn-up for dedicated transit and protected transit customers.
Examples
How customers use the communities.
Emergency host blackhole
Route
203.0.113.44/32Communities
65535:666Traffic to the single attacked host is discarded at the TMW edge while the covering /24 remains online.
Keep route on backup circuit
Route
203.0.113.0/24Communities
215828:70 215828:103Route stays reachable but is low-preference inside AS215828 and heavily prepended externally.
Protected remote handoff
Route
198.51.100.0/24Communities
215828:300 215828:301Prefix enters the mitigation policy and clean traffic is forwarded only to the configured GRE/IPIP endpoint.
Customer ASN
Send your ASN, prefix list, and AS-SET before the first production announcement.
Route objects
Create route/route6 objects for every prefix and make ROAs valid before cutover.
Protected handoff
GRE/IPIP and clean-only communities require an approved endpoint outside the protected prefix.
Change record
Reference a ticket or maintenance window when using customer maintenance controls.
Production note
Do not test blackhole or export-suppression communities on production prefixes without a NOC change window. TMW can provide a lab prefix for validation during onboarding.
Need a custom export policy?
TMW can add per-upstream, per-IX, or per-region communities during customer turn-up when the routing policy is documented in the order or NOC ticket.