RIS Peering Policy
Please announce all your IPv4 and IPv6 BGP routes to the RRC. With this information, our global visibility calculations become more accurate and it helps other AS operators to ensure that their prefixes are visible on your network. The use of TCP MD5 signatures is not supported. Participating peers will be listed on the RIS webpages. All BGP traffic will be recorded, stored in the RIS Database and made available to the Internet community.
If you have questions about details, please do not hesitate to contact us for guidance.
Expect to see a small number of prefixes (a subset of those listed in the AS12654:RS-RIS object in the RIPE Database) being announced in your direction. These are "Routing Beacons", mainly used for BGP convergence and flap damping studies. If possible, please treat the beacon prefixes as normal customer prefixes by providing transit for them and announcing them to your peers, customers and transit providers as appropriate. Only a very small amount of traffic to or from these prefixes may be seen while they are used for reachability tests.
- For peering with the RIS project, use our peering form.
- To contact us about peering or other issues, send an e-mail to ris _at_ ripe _dot_ net.
RRCs Locations Map
Peering information for all RRCs:
|RRC00||RIPE NCC, Amsterdam||12654||22.214.171.124||2001:67c:2e8:2:ffff:0:4:28|
NL-IX, The Hague
|RRC11||NYIIX, New York||12654||126.96.36.199||2001:504:1:0:0:A501:2654:1|
|RRC14||PAIX, Palo Alto||12654||188.8.131.52||2001:504:d::9|
|RRC15||PTTMetro-SP, Sao Paulo||12654||184.108.40.206||2001:12f8::23|
|RRC19||NAP Africa JB, Johannesburg||12654||220.127.116.11