RS-Media: PeeringDB fix list
AS197309 · peeringdb.com/net/19283
2 things to fix in RS-Media's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on RS-Media'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 (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 2a03:5f80:4::224:240 Port speed differs 200G 210G - In the entry with IPv4 178.18.224.240: set IPv6 to 2a03:5f80:4::224:240 (now empty); set Speed to 210000 (210G) (now 200000).
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 IPv4 address missing from PeeringDB 195.208.210.61 195.208.210.61 195.208.210.178 - Add an entry: IPv4 195.208.210.178, IPv6 –, 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.
From ixreport.com/net/197309/: 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.