This is a beta/testing instance of PeeringDB. Some features may work differently than production. Do not store data here that you intend to keep - automatically scheduled refreshes from production are currently disabled.

Database last synchronized at 2024-02-21 01:02:44

RTIX Route Servers
Also Known As
RTIX
Long Name
ASN
207800
IRR as-set/route-set
RIPE::AS207800:AS-RTIX-SET
Route Server URL
Looking Glass URL
Network Types
Route Server
IPv4 Prefixes
160000
IPv6 Prefixes
80000
Traffic Levels
Not Disclosed
Traffic Ratios
Not Disclosed
Geographic Scope
Europe
Protocols Supported
Unicast IPv4 Multicast IPv6 Never via route servers
Last Updated
2023-05-03T06:17:31Z
Public Peering Info Updated
2022-03-14T14:36:14Z
Peering Facility Info Updated
Contact Info Updated
2022-03-14T14:35:17Z
Notes
To join in RTIX write to **help@ria.ee** # Community based prefix filtering The RTIX route server system also provides well known communities to allow members to control the distribution of their prefixes. These communities are defined as follows: - Prevent announcement of a prefix to a peer: **0:peer-as** - Announce a route to a certain peer: **1:peer-as** - Prevent announcement of a prefix to all peers: **0:0** - Announce a route to all peers: **1:1** To instruct the route servers to distribute a particular prefix only to AS64111 and AS64222, the prefix should be tagged with communities: **0:0**, **1:64111** and **1:64222** Alternatively, to announce a prefix to all RTIX members, excluding AS64333, the prefix should be tagged with community **0:64333**. The RTIX route server supports BGP large community prefix distribution control, using the following policy: - Prevent announcement of a prefix to a peer: **207800:0:peer-as** - Announce a route to a certain peer: **207800:1:peer-as** - Prevent announcement of a prefix to all peers: **207800:0:0** - Announce a route to all peers: **207800:1:1** ## Filtering Policy 1. Drop all well-known martians and bogons. 2. Ensure that the peer AS is the same as the first AS in the AS path. 3. Drop any prefix with a transit network ASN in the AS path. 4. If the prefix is evaluated as RPKI valid, accept. 5. If the prefix is evaluated as RPKI invalid, drop.
RIR Status
ok
RIR Status Updated
2024-01-24T04:50:42Z
Peering Policy Information
General Policy
Open
Multiple Locations
Not Required
Ratio Requirement
No
Contract Requirement
Not Required
Health Check
Contact Information
Role
Name
Visiblity
Phone
E-Mail
29470
NOC
NOC
NOC
+3726630299
Public Peering Exchange Points
Exchange
IPv4
ASN
IPv6
Speed
RS Peer
No filter matches.
You may filter by Exchange, ASN or Speed.
29470
538
207800
Operational
10G
RS PEER
213.184.52.1
2001:7f8:50:1::1
29470
538
207800
Operational
10G
RS PEER
213.184.52.254
2001:7f8:50:1:ffff:ffff:ffff:fffe
Interconnection Facilities
Facility
ASN
Country
City
No filter matches.
You may filter by Facility, ASN, Country or City.
Operational