Inter.link: PeeringDB fix list

AS5405 · peeringdb.com/net/28340

PeeringDB

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

Make the changes on Inter.link'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 (2)

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

  1. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847From its IX-F export
    IPv4195.69.119.180
    IPv62001:7f8:d:fb::180
    SpeedNot published
    RS peerYes
  2. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.180
    IPv62001:7f8:d:fc::180
    SpeedNot published
    RS peerYes

Check these entries (1)

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

  1. Germany Community-IX Berlin, Frankfurt, Germany · PeeringDB 1329Not on its website members list
    IPv4185.1.74.6
    IPv62001:7f8:a5::5405:1
    Speed100000 Mbps (100G)

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

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