GVA: PeeringDB fix list
AS36924 · peeringdb.com/net/10626
One thing to fix in GVA's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on GVA'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 196.223.12.150 196.223.12.150 196.223.12.151 IPv6 address missing from PeeringDB 2001:43f8:150::150 2001:43f8:150::150 2001:43f8:150::151 Port speed differs 1G 2 × 1G - Add an entry: IPv4 196.223.12.151, IPv6 2001:43f8:150::151, speed 1000 (1G), RS peer no.
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/36924/: 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.