Belcenter: PeeringDB fix list

AS31449 · peeringdb.com/net/2625

PeeringDB

6 things to fix in Belcenter's PeeringDB record, from what its exchanges publish: 1 to add, 5 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on Belcenter's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

Add these exchanges (1)

On the exchange's own member list, but not in Belcenter's PeeringDB record. Add one entry per connection with these values.

  1. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70From its IX-F export
    IPv4194.68.123.208
    IPv62001:7f8:d:ff::208
    Speed2000000 Mbps (2T)
    RS peerYes

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
    IPv6 address missing from PeeringDBnone2001:7f8:1::a503:1449:1
    • In the entry with IPv4 80.249.210.71: set IPv6 to 2001:7f8:1::a503:1449:1 (now empty).

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

  2. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8::7ad9:0:1
    Port speed differs200M100G
    • In the entry with IPv4 80.81.195.2: set IPv6 to 2001:7f8::7ad9:0:1 (now empty); set Speed to 100000 (100G) (now 200).
  3. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4::7ad9:1
    • In the entry with IPv4 195.66.231.64: set IPv6 to 2001:7f8:4::7ad9:1 (now empty).
  4. Luxembourg LU-CIX Luxembourg, Luxembourg · PeeringDB 297
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:4c::7ad9:1
    • In the entry with IPv4 188.93.170.58: set IPv6 to 2001:7f8:4c::7ad9:1 (now empty).

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

  5. ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:fe::208
    Port speed differs100M2T
    • In the entry with IPv4 194.68.128.208: set IPv6 to 2001:7f8:d:fe::208 (now empty); set Speed to 2000000 (2T) (now 100).

From ixreport.com/net/31449/: 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.