SC MEDIA SUD: PeeringDB fix list
AS50604 · peeringdb.com/net/18530
One thing to fix in SC MEDIA SUD's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on SC MEDIA SUD'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 (1)
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 IPv4 address missing from PeeringDB 86.104.125.75 86.104.125.75 86.104.125.198 IPv6 address missing from PeeringDB none 2001:7f8:64:225:0:5:604:1 2001:7f8:64:225:0:5:604:2 Port speed differs 4G 2 × 10G - In the entry with IPv4 86.104.125.75: set IPv6 to 2001:7f8:64:225:0:5:604:1 (now empty); set Speed to 10000 (10G) (now 4000).
- Add an entry: IPv4 86.104.125.198, IPv6 2001:7f8:64:225:0:5:604:2, speed 10000 (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.
From ixreport.com/net/50604/: 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.