Beltelecom: PeeringDB fix list

AS6697 · peeringdb.com/net/11549

PeeringDB

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

Make the changes on Beltelecom'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 (3)

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

  1. Germany DE-CIX Dusseldorf Düsseldorf, Germany · PeeringDB 1214From its IX-F export and website members list
    IPv4185.1.170.38
    IPv62001:7f8:9e::1a29:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  2. Germany DE-CIX Hamburg Hamburg, Germany · PeeringDB 74From its IX-F export and website members list
    IPv4185.1.210.45
    IPv62001:7f8:3d::1a29:0:1
    Speed100000 Mbps (100G)
    RS peerYes
  3. Germany DE-CIX Munich Munich, Germany · PeeringDB 248From its IX-F export and website members list
    IPv4185.1.208.48
    IPv62001:7f8:44::1a29:0:1
    Speed100000 Mbps (100G)
    RS peerYes

Correct these entries (2)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs40G100G
    • In the entry with IPv4 80.81.194.197: set Speed to 100000 (100G) (now 40000).
  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB178.18.225.215178.18.224.17 178.18.225.215 178.18.227.34
    IPv6 address missing from PeeringDB2a03:5f80:4::225:2152a03:5f80:4::224:17 2a03:5f80:4::225:215 2a03:5f80:4::227:34
    Port speed differs60G80G + 2 × 40G
    • In the entry with IPv4 178.18.225.215: set Speed to 80000 (80G) (now 60000).
    • Add an entry: IPv4 178.18.227.34, IPv6 2a03:5f80:4::227:34, speed 40000 (40G), RS peer yes.
    • Add an entry: IPv4 178.18.224.17, IPv6 2a03:5f80:4::224:17, speed 40000 (40G), 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/6697/: 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.