ixreport

Neterra: PeeringDB fix list

AS34224 · peeringdb.com/net/2033

PeeringDB

5 things to fix in Neterra's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 22:13 UTC.

Make the changes on Neterra'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 (5)

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. Netherlands AMS-IX Amsterdam, Netherlands · PeeringDB 26
    ProblemPeeringDB hasThe export has
    Port speed differs20G10G
    • In the entry with IPv4 80.249.209.26: set Speed to 10000 (10G) (now 20000).

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Bulgaria BIX.BG Sofia, Bulgaria · PeeringDB 331
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB193.169.198.206193.169.198.206 193.169.198.207 193.169.198.226
    IPv6 address missing from PeeringDBnone2001:7f8:58::85b0:0:1 2001:7f8:58::85b0:0:2 2001:7f8:58::85b0:0:3
    • In the entry with IPv4 193.169.198.206: set IPv6 to 2001:7f8:58::85b0:0:1 (now empty).
    • Add an entry: IPv4 193.169.198.207, IPv6 2001:7f8:58::85b0:0:2.
    • Add an entry: IPv4 193.169.198.226, IPv6 2001:7f8:58::85b0:0:3.
  3. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 80.81.192.77: set Speed to 100000 (100G) (now 30000).
  4. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs10G4G
    • In the entry with IPv4 195.66.225.156: set Speed to 4000 (4G) (now 10000).
  5. Bulgaria NetIX Sofia, Bulgaria · PeeringDB 699
    ProblemPeeringDB hasThe export has
    IPv4 address in PeeringDB, not in the export185.1.226.9 185.1.226.10 185.1.226.11 185.1.226.12185.1.226.9 185.1.226.10 185.1.226.11
    IPv6 address in PeeringDB, not in the export2001:67c:29f0::3:4224:1 2001:67c:29f0::3:4224:2 2001:67c:29f0::3:4224:3 2001:67c:29f0::3:4224:42001:67c:29f0::3:4224:1 2001:67c:29f0::3:4224:3 2001:67c:29f0::3:4224:4
    • In the entry with IPv4 185.1.226.10: set IPv6 to 2001:67c:29f0::3:4224:4 (now 2001:67c:29f0::3:4224:2).
    • The entry with IPv4 185.1.226.12, IPv6 2001:67c:29f0::3:4224:4 isn't in the export: delete it if that connection is gone.

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