RIPE NCC K-Root Operations: PeeringDB fix list
AS25152 · peeringdb.com/net/1486
14 things to fix in RIPE NCC K-Root Operations's PeeringDB record, from what its exchanges publish: 7 to add, 7 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on RIPE NCC K-Root Operations'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 (7)
On the exchange's own member list, but not in RIPE NCC K-Root Operations's PeeringDB record. Add one entry per connection with these values.
-
IPv4 103.27.170.75 IPv6 2401:7500:fff6::122 Speed 1000 Mbps (1G) RS peer Yes -
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
-
IPv4 206.71.8.19 IPv6 2001:504:68::19 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 206.80.232.19 IPv6 2001:504:67::19 Speed 10000 Mbps (10G) RS peer Yes -
IPv4 45.68.40.146 IPv6 2801:1f5::146 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.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 193.178.185.126: 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 198.179.18.137: 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 IPv6 address differs 2001:504:44::2:5152:1 2001:504:44::6240:0:1 - In the entry with IPv4 206.53.137.20: set IPv6 to 2001:504:44::6240:0:1 (now 2001:504:44::2:5152:1).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 103.142.153.17: 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.96.44: 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 217.29.66.8: set Speed to 10000 (10G) (now 1000).
-
Problem PeeringDB has The export has Port speed differs 1G 10G - In the entry with IPv4 196.60.9.80: 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.
From ixreport.com/net/25152/: 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.