ixreport

Core-Backbone: PeeringDB fix list

AS33891 · peeringdb.com/net/1599

PeeringDB

9 things to fix in Core-Backbone's PeeringDB record, from what its exchanges publish: 4 to add, 5 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Core-Backbone'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 (4)

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

  1. Japan BBIX Tokyo Tokyo, Japan · PeeringDB 126From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Germany DE-CIX Leipzig Leipzig, Germany · PeeringDB 4004From its IX-F export and website members list
    IPv4185.1.245.14
    IPv62001:7f8:df::8463:0:1
    Speed400000 Mbps (400G)
    RS peerYes
  3. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.117
    IPv62001:7f8:d:fb::117
    Speed50000000 Mbps (50T)
    RS peerYes
  4. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.117
    IPv62001:7f8:d:fc::117
    Speed50000000 Mbps (50T)
    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. Germany BCIX Berlin, Germany · PeeringDB 87
    ProblemPeeringDB hasThe export has
    Port speed differs100G30G
    • In the entry with IPv4 193.178.185.44: set Speed to 30000 (30G) (now 100000).

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

  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 400G400G

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

  3. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs100G50T
    • In the entry with IPv4 194.68.128.117: set Speed to 50000000 (50T) (now 100000).
  4. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs100G50T
    • In the entry with IPv4 194.68.123.117: set Speed to 50000000 (50T) (now 100000).
  5. Czechia Peering.cz Prague, Bratislava, Vienna, Frankfurt, Czechia · PeeringDB 713
    ProblemPeeringDB hasThe export has
    Port speed differs100G12.5G
    • In the entry with IPv4 185.0.20.30: set Speed to 12500 (12.5G) (now 100000).

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