Transit Import Filters
Routes from transit providers are processed through the following sequential filters:
Default Route
Blocked
IP Bogon
Blocked
AS Bogon
Blocked
BGP Path > 50
Blocked
RPKI Invalid
Blocked
Prefix Length
(IPv4 </24, IPv6 </48 Blocked)
Transit Export Filters
Before propagation, transit routes undergo these sequential export filters:
Default
Blocked
IP Bogon
Blocked
AS Bogon
Blocked
BGP Path > 50
Blocked
Bad Prefix Length
Blocked
RPKI Invalid
Blocked
Downstream Import Filters
For routes imported from downstream, the following filters are applied sequentially:
ASN_BOGON
Blocked
BGP Path > 50
Blocked
Bad Prefix Length
Blocked
Bogon IP
Blocked
RPKI Invalid
Blocked
Not in Allowed Prefixes
Blocked
Accepted Route
Large community added, local_pref=1000
Communities
Each community tag instructs specific routing actions. Tap on a card for details.
Action Communities
6517:0:<dstasn>
Do not announce to the specified AS.
6517:1:<dstasn>
Prepend the AS once.
6517:2:<dstasn>
Prepend the AS twice.
6517:3:<dstasn>
Prepend the AS three times.
Information Communities
6517:100:<x>
Indicates the route was imported from upstream.
6517:200:<x>
Indicates the route was imported from an IX.
6517:300:<x>
Indicates the route was imported from downstream.
6517:400:<x>
Indicates the route was imported from a peer.
Our providers
We maintain direct sessions with various upstreams, peers, and IXes. Below is a quick overview:
| AS Number | Type (IX/Peer/Upstream) | Capacity | Description |
|---|---|---|---|
| 41720 | Upstream | 10 Gbps | Main uplink in CO-1 |
| 212516 | Upstream | 1 Gbps | Backup uplink in CO-1 |
| 211138 | Upstream | 1 Gbps | DDoS protected uplink in CO-1 |
IRR Filters
We automatically generate IRR-based prefix filters every 6 hours, aggregating data from:
RPKI, AFRINIC, ARIN, APNIC, LACNIC, RIPE.
RADB is considered a higher-risk IRR, so it requires manual verification. If you need to force the usage of RADB, please open a support ticket explaining why you must use RADB.