RIPE NCC RIS Project
AS12654
RIPE NCC
Tools: Where can I peer with RIPE NCC RIS Project? · Where should RIPE NCC RIS Project peer next? · Compare RIPE NCC RIS Project with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
8 things to fix in RIPE NCC RIS Project's PeeringDB record, from what its exchanges publish: 7 to correct, 1 to check. As of 2026-11-19 12:40 UTC.
Make the changes on RIPE NCC RIS Project's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (7)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 80.249.208.69: set Speed to 10000 (10G) (now 1000).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 193.242.98.118: set Speed to 1000 (1G) (now 100).
PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
Problem PeeringDB has The export has Port speed differs 100M 1G - In the entry with IPv4 192.65.185.40: set Speed to 1000 (1G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 80.81.192.152: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 195.66.225.241: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 100M 10G - In the entry with IPv4 217.29.66.6: set Speed to 10000 (10G) (now 100).
-
Problem PeeringDB has The export has Port speed differs 1G 200G - In the entry with IPv4 185.1.8.106: set Speed to 200000 (200G) (now 1000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If RIPE NCC RIS Project has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 194.68.123.147 IPv6 2001:7f8:d:ff::147 Speed 100 Mbps (100M)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 25 |
| Nov 18, 2026 | 25 |
| Nov 17, 2026 | 25 |
| Nov 16, 2026 | 25 |
| Nov 15, 2026 | 25 |
| Nov 14, 2026 | 25 |
| Nov 13, 2026 | 25 |
| Nov 12, 2026 | 25 |
| Nov 11, 2026 | 25 |
| Nov 10, 2026 | 25 |
| Nov 9, 2026 | 25 |
| Nov 8, 2026 | 25 |
| Nov 7, 2026 | 25 |
| Nov 6, 2026 | 25 |
| Nov 5, 2026 | 25 |
| Nov 4, 2026 | 25 |
| Nov 3, 2026 | 25 |
| Nov 2, 2026 | 25 |
| Nov 1, 2026 | 25 |
| Oct 31, 2026 | 25 |
| Oct 30, 2026 | 25 |
| Oct 29, 2026 | 25 |
| Oct 28, 2026 | 25 |
| Oct 27, 2026 | 25 |
| Oct 26, 2026 | 25 |
| Oct 25, 2026 | 25 |
| Oct 24, 2026 | 25 |
| Oct 23, 2026 | 25 |
| Oct 22, 2026 | 25 |
| Oct 21, 2026 | 25 |
| Oct 20, 2026 | 25 |
| Oct 19, 2026 | 25 |
| Oct 18, 2026 | 25 |
| Oct 17, 2026 | 25 |
| Oct 16, 2026 | 25 |
| Oct 15, 2026 | 25 |
| Oct 14, 2026 | 25 |
| Oct 13, 2026 | 25 |
| Oct 12, 2026 | 25 |
| Oct 11, 2026 | 25 |
| Oct 10, 2026 | 25 |
| Oct 9, 2026 | 25 |
| Oct 8, 2026 | 25 |
| Oct 7, 2026 | 25 |
| Oct 6, 2026 | 25 |
| Oct 5, 2026 | 25 |
| Oct 4, 2026 | 25 |
| Oct 3, 2026 | 25 |
Map
Where RIPE NCC RIS Project's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.
| AMS-IX Amsterdam, Netherlands | 1G | Both Speed differs | |
| CATNIX Barcelona, Spain | 100M | Both Speed differs | |
| CIXP Geneva, Switzerland | 100M | Both Speed differs | |
| DE-CIX Frankfurt Frankfurt, Germany | 1G | Both Speed differs | |
| DIX-IE Tokyo, Japan | 100M | PeeringDB | |
| Equinix Miami Miami, United States | 100M | PeeringDB | |
| Equinix Palo Alto Palo Alto, United States | 100M | PeeringDB | |
| Equinix Singapore Singapore, Singapore | 1G | PeeringDB | |
| France-IX Marseille Marseille, France | 1G | PeeringDB | |
| France-IX Paris Paris, France | 1G | PeeringDB | |
| InterLAN-IX Bucharest, Romania | 1G | Both | |
| IX.br (PTT.br) São Paulo São Paulo/SP, Brazil | 100M | Both | |
| JPIX TOKYO Tokyo, Japan | 10G | Both | |
| LINX LON1 London, United Kingdom | 1G | Both Speed differs | |
| LONAP London, United Kingdom | 10G | Both | |
| LU-CIX Luxembourg, Luxembourg | 100M | Both | |
| MIX-IT Milan, Italy | 100M | Both Speed differs | |
| MSK-IX Moscow Moscow, Russia | 100M | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 1G | Both | |
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 100M | PeeringDB only | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 100M | Both | |
| NYIIX New York New York, United States | 100M | PeeringDB | |
| SwissIX Zurich, Switzerland | 1G | Both | |
| UAE-IX Dubai, United Arab Emirates | 1G | Both Speed differs | |
| VIX Vienna, Austria | 10G | Both |
RIPE NCC RIS Project lists no facilities in PeeringDB.
Recent changes Search them
- Nov 6, 2026 [PDB] AS12654 RIPE NCC RIS Project no longer in PeeringDB at CATNIX (still on its IX-F list)