Pangea Connected: PeeringDB fix list
AS207456 · peeringdb.com/net/30233
2 things to fix in Pangea Connected's PeeringDB record, from what its exchanges publish: 1 to correct, 1 to check. As of 2026-10-08 20:58 UTC.
Make the changes on Pangea Connected'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 195.66.227.227 195.66.227.227 195.66.231.60 IPv6 address missing from PeeringDB none 2001:7f8:4::3:2a60:1 2001:7f8:4::3:2a60:2 Port speed differs 10G 4G + 1G - In the entry with IPv4 195.66.227.227: set IPv6 to 2001:7f8:4::3:2a60:1 (now empty); set Speed to 4000 (4G) (now 10000).
- Add an entry: IPv4 195.66.231.60, IPv6 2001:7f8:4::3:2a60:2, speed 1000 (1G), RS peer yes.
Check these entries (1)
In PeeringDB, but on none of the exchange's own lists. If Pangea Connected has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.
-
IPv4 195.66.236.191 IPv6 – Speed 10000 Mbps (10G)
From ixreport.com/net/207456/: 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.