Citadel Investment Group: PeeringDB fix list
AS13631 · peeringdb.com/net/28509
2 things to fix in Citadel Investment Group's PeeringDB record, from what its exchanges publish: 2 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on Citadel Investment Group'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 in PeeringDB, not in the export 2001:504:40:108::1:224 none - In the entry with IPv4 206.41.108.224: set IPv6 to (empty) (now 2001:504:40:108::1:224).
-
Problem PeeringDB has The export has IPv6 address in PeeringDB, not in the export 2001:7f8:17::353f:1 none Port speed differs 10G 5G - In the entry with IPv4 5.57.80.235: set IPv6 to (empty) (now 2001:7f8:17::353f:1); set Speed to 5000 (5G) (now 10000).
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/13631/: 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.