RIPE NCC Authoritative DNS: PeeringDB fix list
AS197000 · peeringdb.com/net/3859
10 things to fix in RIPE NCC Authoritative DNS's PeeringDB record, from what its exchanges publish: 4 to add, 3 to correct, 3 to check. As of 2026-10-08 18:53 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 (4)
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.
-
IPv4 45.186.143.21 IPv6 2801:80:37a0::a519:7000:1 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.
Correct these entries (3)
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 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 (3)
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 210.173.177.125 IPv6 2001:7fa:7:1:0:19:7000:1 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)
From ixreport.com/net/197000/: PeeringDB against each exchange's IX-F export and website members list. Exchanges whose lists couldn't be read on this update aren't included.