Interlan Networks: PeeringDB fix list

AS43065 · peeringdb.com/net/20639

PeeringDB

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

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

  1. Sweden Netnod Sundsvall -- MTU4470 Sundsvall / Gavle, Sweden · PeeringDB 2869From its IX-F export
    IPv4194.68.135.20
    IPv62001:7f8:d:301::20
    Speed2000000 Mbps (2T)
    RS peerYes

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. Sweden Netnod Sundsvall -- MTU1500 Sundsvall / Gavle, Sweden · PeeringDB 194
    ProblemPeeringDB hasThe export has
    Port speed differs2G2T
    • In the entry with IPv4 194.68.133.20: set Speed to 2000000 (2T) (now 2000).

Check these entries (2)

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

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846Not on its IX-F export
    IPv4194.68.128.160
    IPv62001:7f8:d:fe::160
    Speed2000 Mbps (2G)
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70Not on its IX-F export
    IPv4194.68.123.160
    IPv62001:7f8:d:ff::160
    Speed2000 Mbps (2G)

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