G.Network Communications: PeeringDB fix list
AS202596 · peeringdb.com/net/21038
3 things to fix in G.Network Communications's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on G.Network Communications'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 (3)
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 missing from PeeringDB none 2001:7f8:4::3:1764:2 - In the entry with IPv4 195.66.231.20: set IPv6 to 2001:7f8:4::3:1764:2 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:4:1:0:3:1764:1 - In the entry with IPv4 195.66.236.7: set IPv6 to 2001:7f8:4:1:0:3:1764:1 (now empty).
-
Problem PeeringDB has The export has Port speed differs 20G 40G - In the entry with IPv4 5.57.81.163: set Speed to 40000 (40G) (now 20000).
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/202596/: 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.