RIPE NCC Authoritative DNS
AS197000 · f.in-addr-servers.arpa, f.ip6-servers.arpa, pri.authdns.ripe.net, sec1.authdns.ripe.net, sec2.authdns.ripe.net
RIPE NCC
Tools: Where can I peer with RIPE NCC Authoritative DNS? · Where should RIPE NCC Authoritative DNS peer next? · Compare RIPE NCC Authoritative DNS with another network
This network elsewhere: its routes on BGP Report
PeeringDB fix list Printable page · CSV
9 things to fix in RIPE NCC Authoritative DNS's PeeringDB record, from what its exchanges publish: 3 to add, 4 to correct, 2 to check. As of 2026-11-19 12:40 UTC.
Make the changes on RIPE NCC Authoritative DNS's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (3)
On the exchange's own member list, but not in RIPE NCC Authoritative DNS's PeeringDB record. Add one entry per connection with these values.
-
IPv4 193.136.250.207 IPv6 2001:7f8:a:1::207 Speed 1000 Mbps (1G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 45.68.40.147 IPv6 2801:1f5::147 Speed 10000 Mbps (10G) RS peer Yes PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.
Correct these entries (4)
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 103.142.153.16: 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 1G 10G - In the entry with IPv4 196.60.97.119: 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 1G 10G - In the entry with IPv4 163.223.201.41: 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 1G 10G - In the entry with IPv4 196.60.9.32: 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.
Check these entries (2)
In PeeringDB, but on none of the exchange's own lists. If RIPE NCC Authoritative DNS has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 91.218.7.103 IPv6 2001:7f8:94::103 Speed 10000 Mbps (10G) This exchange only publishes a website list, and some leave out members who ask not to be listed.
-
IPv4 194.68.123.174 IPv6 2001:7f8:d:ff::174 Speed 1000 Mbps (1G)
Exchanges over time
Show as a table
| Date | Exchanges |
|---|---|
| Nov 19, 2026 | 38 |
| Nov 18, 2026 | 38 |
| Nov 17, 2026 | 38 |
| Nov 16, 2026 | 38 |
| Nov 15, 2026 | 38 |
| Nov 14, 2026 | 38 |
| Nov 13, 2026 | 38 |
| Nov 12, 2026 | 38 |
| Nov 11, 2026 | 38 |
| Nov 10, 2026 | 38 |
| Nov 9, 2026 | 38 |
| Nov 8, 2026 | 38 |
| Nov 7, 2026 | 38 |
| Nov 6, 2026 | 38 |
| Nov 5, 2026 | 38 |
| Nov 4, 2026 | 38 |
| Nov 3, 2026 | 38 |
| Nov 2, 2026 | 38 |
| Nov 1, 2026 | 37 |
| Oct 31, 2026 | 37 |
| Oct 30, 2026 | 37 |
| Oct 29, 2026 | 37 |
| Oct 28, 2026 | 38 |
| Oct 27, 2026 | 38 |
| Oct 26, 2026 | 38 |
| Oct 25, 2026 | 38 |
| Oct 24, 2026 | 38 |
| Oct 23, 2026 | 38 |
| Oct 22, 2026 | 38 |
| Oct 21, 2026 | 38 |
| Oct 20, 2026 | 39 |
| Oct 19, 2026 | 39 |
| Oct 18, 2026 | 39 |
| Oct 17, 2026 | 39 |
| Oct 16, 2026 | 39 |
| Oct 15, 2026 | 38 |
| Oct 14, 2026 | 38 |
| Oct 13, 2026 | 38 |
| Oct 12, 2026 | 38 |
| Oct 11, 2026 | 38 |
| Oct 10, 2026 | 38 |
| Oct 9, 2026 | 38 |
| Oct 8, 2026 | 38 |
| Oct 7, 2026 | 38 |
| Oct 6, 2026 | 38 |
| Oct 5, 2026 | 38 |
| Oct 4, 2026 | 38 |
| Oct 3, 2026 | 38 |
Map
Where RIPE NCC Authoritative DNS'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.
| AIX Tapos, Depok, Indonesia | 1G | Both | |
| AMS-IX Amsterdam, Netherlands | 10G | Both | |
| ArmIX Yerevan, Armenia | 10G | PeeringDB only | |
| BCIX Berlin, Germany | 10G | Both | |
| BHNIX Sarajevo, Bosnia and Herzegovina | 1G | Both | |
| BKNIX (Thailand) Bangkok, Thailand | 1G | Both | |
| CitraIX Yogyakarta Yogyakarta, Indonesia | 1G | Both | |
| DIX-IE Tokyo, Japan | 10G | PeeringDB | |
| France-IX AURA Lyon and Grenoble, France | 200M | PeeringDB | |
| France-IX Lille Lille, France | 200M | PeeringDB | |
| France-IX Marseille Marseille, France | 200M | PeeringDB | |
| France-IX Paris Paris, France | 200M | PeeringDB | |
| France-IX Toulouse Toulouse, France | 200M | PeeringDB | |
| GigaPIX - LAN 1 Lisbon, Portugal | 1G | Not in PeeringDB | |
| Guam IX Tamuning, Guam | 1G | Both Speed differs | |
| IIX-Jakarta Jakarta, Indonesia | 10G | Both | |
| InterLAN-IX Bucharest, Romania | 2G | Both | |
| JINX Johannesburg, South Africa | 1G | Both Speed differs | |
| JPNAP Tokyo Tokyo, Japan | 10G | PeeringDB | |
| KG-IX Bishkek Bishkek, Kyrgyzstan | 10G | Both | |
| LINX LON1 London, United Kingdom | 10G | Both | |
| LINX LON2 London, United Kingdom | 10G | Both | |
| LONAP London, United Kingdom | 10G | Both | |
| Maharlika IX Manila, Philippines | 1G | Both Speed differs | |
| Namex Rome Rome, Italy | 1G | Both | |
| NAPAfrica IX Johannesburg Johannesburg, South Africa | 1G | Both Speed differs | |
| NAPVE CCS Caracas, Venezuela | 1G | Both | |
| NAPVE MCBO Maracaibo, Venezuela | 1G | PeeringDB | |
| Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden | 1G | PeeringDB only | |
| NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands | 10G | Both | |
| PatagoniaIX Punta Arenas, Chile | 1G | Both | |
| PIT MX Queretaro, Mexico | 1G | PeeringDB | |
| RIX Reykjavik, Iceland | 1G | Both | |
| RUDAKI-IX Kiev, Ukraine | 1G | Both | |
| SAIX Salzburg, Austria | 1G | PeeringDB | |
| SGIX Singapore, Singapore | Website list only | ||
| STIX.DO Santiago, Dominican Republic | 10G | Not in PeeringDB | |
| STUIX Taipei City, Taiwan | 1G | Both |
RIPE NCC Authoritative DNS lists no facilities in PeeringDB.
Recent changes Search them
- Nov 18, 2026 [WEB] AS197000 RIPE NCC Authoritative DNS dropped from NAPAfrica IX Johannesburg's website list (still in PeeringDB and on its IX-F list)
- Oct 19, 2026 [PDB] AS197000 RIPE NCC Authoritative DNS now in PeeringDB at Maharlika IX
- Oct 16, 2026 [IXF] AS197000 RIPE NCC Authoritative DNS added to Maharlika IX