If you see inaccuracies in the results, please visit:
https://www.ripe.net/contact-form?topic=ripe_dbm&show_form=true
Source
Objects returned came from source
RIPE
Terms and Conditions
This is the RIPE Database query service. The objects are in RDAP format.
http://www.ripe.net/db/support/db-terms-conditions.pdf
Notice
==COMMUNITIES==
-----------------------------------------------------
The following communities can be used by members on our route-servers:
CDN Control (handled by AS39801, connected to the RS) :
40027:40000 - DO announce to Netflix OpenConnect Appliance in Lyon
39801:990:0 - DO NOT announce to any local CDN cache
39801:990:1 - DO NOT announce to Netflix Cache [Default]
39801:990:2 - DO NOT announce to Microsoft/Azure Cache
39801:990:3 - DO NOT announce to Apple Cache
39801:990:4 - DO NOT announce to Google GGC
39801:991:0 - DO announce to all local CDN caches
39801:991:1 - DO announce to Netflix OpenConnect cache (and add 40027:40000)
39801:991:2 - DO announce to Microsoft/Azure Cache [Def*]
39801:991:3 - DO announce to Apple Cache [Def*]
39801:991:4 - DO announce to Google GGC [Def*]
[Def*] - Default behaviour, with a few exceptions
Large BGP communities (RFC8092) :
RFC8092 communities ("Large" BGP communities) are the preferred way
of signalling between peers and the RS. Prefer using them !!!
Communities handled by the RS (peers can set on routes announced to the RS):
43100:0:0 = Do NOT send route to any peer unless explicitly signaled
43100:0:peeras = Do NOT send route to this peer AS
43100:1:0 = DO Send route to all peers [DEFAULT]
43100:1:peeras = DO Send route to this peer AS (if 43100:0:0 specified)
43100:101:peeras = Prepend 1x to this peer AS
43100:102:peeras = Prepend 2x to this peer AS
43100:103:peeras = Prepend 3x to this peer AS
43100:901:peeras = Set MED to 50 for this peer AS
43100:902:peeras = Set MED to 100 for this peer AS
43100:903:peeras = Set MED to 200 for this peer AS
Communities set by the RS (on routes peers receive):
43100:1000:1 = RPKI : Valid ROA (ROA Valid)
43100:1000:2 = RPKI : No ROA Present (RPKI Unknown)
43100:1001:1 = IRR Valid (Origin in AS-Set and route object present)
43100:1001:6 [*] = IRR NotFound : No IRR route object for prefix
Communities for filtered routes, only visible on looking-glass:
(routes tagged with these communities are NOT re-announced to RS peers)
43100:1000:4 = RPKI Invalid
43100:1001:4 = IRR Invalid/NotFound
43100:1001:5 = IRR Invalid - Origin AS not in peer's AS-Set
43100:1101:9 = FILTERED : IRR Invalid/NotFound
43100:1101:10 = FILTERED : IRR Invalid - Origin AS not in peer's AS-Set
43100:1101:11 = FILTERED : IRR NotFound (No route and no valid ROA for prefix)
43100:1101:13 = FILTERED : RPKI Invalid
43100:1101:14 = FILTERED : "Never via RS" ASn in AS-Path
[*] = A route without a valid IRR route object is only re-announced if:
- the origin AS is in the peer's AS-Set
- AND there is a VALID ROA for the origin AS
Legacy/"standard" BGP communities (RFC1997):
RFC1997 BGP communities are still accepted, but their use will be
reduced progressively. Please use RFC8092 "Large" communities instead.
0:peer-as = Do NOT send route to this peer as
0:43100 = Do NOT send route to any peer
43100:peer-as = DO Send route to this peer as
43100:43100 = DO Send route to all peers (default)
Communities added by route-servers
43100:64621 = Prefix received from a peer on RS1 Lyon
43100:64622 = Prefix received from a peer on RS2 Lyon
43100:65011 = Prefix is present in an AS's announced AS/AS-SET
43100:65012 = Prefix has RPKI status: VALID
43100:65023 = Prefix has RPKI status: UNKNOWN
Communities indicating where the peer is physically connected:
43100:64652 = [Local] Prefix received from a FranceIX Lyon/AURA peer
43100:64648 = [Remote] Prefix received from a FranceIX Lille peer
43100:64649 = [Remote] Prefix received from a FranceIX Marseille peer
43100:64650 = [Remote] Prefix received from a FranceIX Paris peer
43100:64655 = [Remote] Prefix received from a FranceIX Toulouse peer
All BGP communities of the form 43100:1nn0, 43100:7nn0, 43100:8nn0 and 43100:9nn0
are deprecated and ignored. STOP using them.
FOR REFERENCE ONLY ! NO LONGER SUPPORTED ! DO NOT USE !
43100:9020 do not send the route to TopIX members
43100:9110 do not send the route to France-IX Paris members
43100:9180 do not send the route to AuvernIX members
-------------------------------------------------------------
Routes rejected:
- Prefix too short : IPv4 : </8 , IPv6 : </19 (default route included)
- Prefix too long : IPv4 : >/24, IPv6 : >/48
- RFC5735 prefixes for IPv4 (includes RFC1918, RFC6598, and others)
- RFC5156 prefixes for IPv6
- RFC6996 - routes containing private ASNs in path
- RPKI Invalid - routes having ROAs, and no ROA matches the announce
- IRR AS Invalid - routes whose origin is NOT in Peers AS-Set
- Invalid origin - routes that have NO valid ROA and NO matching IRR route object
- routes where next_hop != announcing_peer
- routes where first_ASN != peer_ASN
- routes already having the OTC attribute (RFC9234) set
We support ADD-PATHS. If negotiated via BGP, you will receive extended NLRI.
We support RFC9234 - our role is RS_Server.
We set the OTC attribute
If you implement RFC9234 your role will be RS_Client
==PEERS==
==END PEERS==
