BACKBONE.direct: PeeringDB fix list

AS50917 · peeringdb.com/net/30501

PeeringDB

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

Make the changes on BACKBONE.direct'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 BACKBONE.direct's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands INTERIX Amsterdam, Netherlands · PeeringDB 3990From its IX-F export and website members list

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

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

  2. France nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France · PeeringDB 4705From its IX-F export
    IPv4185.1.14.155
    IPv62001:7f8:12e::5:917:1
    Speed100000 Mbps (100G)
    RS peerYes

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

  3. Netherlands NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members list
    IPv4193.239.118.55
    IPv62001:7f8:13::a521:397:1
    SpeedNot published
    RS peerYes

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

Correct these entries (1)

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 GNM-IX Amsterdam, Netherlands · PeeringDB 358
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 100G100G

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

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If BACKBONE.direct has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Netherlands NSIX Amsterdam Amsterdam, Netherlands · PeeringDB 4589Not on its website members list
    IPv4193.192.12.13
    IPv62001:7f8:130::c6e5:1
    Speed10000 Mbps (10G)

    This exchange only publishes a website list, and some leave out members who ask not to be listed.

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