Multichoice Support Services: PeeringDB fix list
AS328045 · peeringdb.com/net/13080
2 things to fix in Multichoice Support Services's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Multichoice Support Services'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 2001:43f8:6d1::70:104 2001:43f8:6d1::70:204 Port speed differs 2 × 100G 2 × 200G - In the entry with IPv4 196.60.70.104: set IPv6 to 2001:43f8:6d1::70:104 (now empty); set Speed to 200000 (200G) (now 100000).
- In the entry with IPv4 196.60.70.204: set IPv6 to 2001:43f8:6d1::70:204 (now empty); set Speed to 200000 (200G) (now 100000).
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 missing from PeeringDB none 2001:43f8:6d0::9:52 2001:43f8:6d0::9:152 Port speed differs 2 × 100G 2 × 400G - In the entry with IPv4 196.60.9.152: set IPv6 to 2001:43f8:6d0::9:152 (now empty); set Speed to 400000 (400G) (now 100000).
- In the entry with IPv4 196.60.9.52: set IPv6 to 2001:43f8:6d0::9:52 (now empty); set Speed to 400000 (400G) (now 100000).
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/328045/: 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.