ASPA CLOUD: PeeringDB fix list
AS202207 · peeringdb.com/net/31257
One thing to fix in ASPA CLOUD's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on ASPA CLOUD'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 185.1.193.2 185.1.192.190 185.1.193.2 IPv6 address missing from PeeringDB 2001:7f8:a0:0:3:15df:0:2 2001:7f8:a0:0:3:15df:0:1 2001:7f8:a0:0:3:15df:0:2 Port speed differs 10G 10G + 1G - Add an entry: IPv4 185.1.192.190, IPv6 2001:7f8:a0:0:3:15df:0:1, speed 1000 (1G), RS peer yes.
From ixreport.com/net/202207/: 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.