Global Communication Net AD: PeeringDB fix list

AS12615 · peeringdb.com/net/2310

PeeringDB

3 things to fix in Global Communication Net AD's PeeringDB record, from what its exchanges publish: 3 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Global Communication Net AD'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.

  1. Bulgaria B-IX Sofia, Bulgaria · PeeringDB 326
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB185.1.30.16185.1.30.16 185.1.30.131
    • Add an entry: IPv4 185.1.30.131, IPv6 –, speed 10000 (10G), RS peer yes.
  2. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.169.198.156193.169.198.156 193.169.198.157
    IPv6 address missing from PeeringDB2001:7f8:58::3147:0:12001:7f8:58::3147:0:1 2001:7f8:58::3147:0:2
    • Add an entry: IPv4 193.169.198.157, IPv6 2001:7f8:58::3147:0:2.
  3. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.236.48178.18.236.48 178.18.236.127
    IPv6 address missing from PeeringDB2a03:5f80:4:2::236:482a03:5f80:4:2::236:48 2a03:5f80:4:2::236:127
    • Add an entry: IPv4 178.18.236.127, IPv6 2a03:5f80:4:2::236:127, speed 10000 (10G), RS peer yes.

    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/12615/: 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.