Community IX Holdings: PeeringDB fix list
AS63221 · peeringdb.com/net/8559
3 things to fix in Community IX Holdings's PeeringDB record, from what its exchanges publish: 2 to correct, 1 to check. As of 2026-10-08 18:53 UTC.
Make the changes on Community IX Holdings'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 IPv4 address in PeeringDB, not in the export 149.112.69.4 149.112.69.5 none IPv6 address in PeeringDB, not in the export 2001:504:40:69::1:4 2001:504:40:69::1:5 none - The entry with IPv4 149.112.69.4, IPv6 2001:504:40:69::1:4 isn't in the export: delete it if that connection is gone.
- The entry with IPv4 149.112.69.5, IPv6 2001:504:40:69::1:5 isn't in the export: delete it if that connection is gone.
-
Problem PeeringDB has The export has Port speed differs 2 × 100G 2 × 10G - In the entry with IPv4 206.41.108.4: set Speed to 10000 (10G) (now 100000).
- In the entry with IPv4 206.41.108.5: set Speed to 10000 (10G) (now 100000).
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Community IX Holdings has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 206.71.12.4 IPv6 2001:504:40:12::1:4 Speed 100000 Mbps (100G) IPv4 206.71.12.5 IPv6 2001:504:40:12::1:5 Speed 100000 Mbps (100G)
From ixreport.com/net/63221/: 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.