ST Digital: PeeringDB fix list
AS328840 · peeringdb.com/net/26665
One thing to fix in ST Digital's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on ST Digital'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 Address belongs to another network in PeeringDB 196.60.84.81 is AS37672 INQ DIGITAL CAMEROON SA 196.60.84.81 IPv6 address differs 2001:43fd:c000:d0a1::61 2001:43fd:c000:d0ae::61 IPv4 address in PeeringDB, not in the export 196.60.84.61 196.60.84.81 Port speed differs 100M 10G + 100M An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 196.60.84.61: set IPv4 to (empty) (now 196.60.84.61); set IPv6 to 2001:43fd:c000:d0ae::61 (now 2001:43fd:c000:d0a1::61); set Speed to 10000 (10G) (now 100).
From ixreport.com/net/328840/: 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.