RTE Group: PeeringDB fix list
AS398042 · peeringdb.com/net/23023
3 things to fix in RTE Group's PeeringDB record, from what its exchanges publish: 1 to add, 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on RTE Group'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 (1)
On the exchange's own member list, but not in RTE Group's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.48.59 IPv6 2001:7f8:3f:0:6:12da:0:1 Speed 10000 Mbps (10G) RS peer Yes
Correct these entries (2)
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 IPv6 address missing from PeeringDB none 2001:7f8::6:12da:0:2 - In the entry with IPv4 80.81.195.68: set IPv6 to 2001:7f8::6:12da:0:2 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB 2001:504:36:0:6:12da:0:1 2001:504:36:0:6:12da:0:1 2001:504:36:0:6:12da:0:2 - In the entry with IPv4 206.82.105.37: set IPv6 to 2001:504:36:0:6:12da:0:2 (now empty).
From ixreport.com/net/398042/: 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.