ITM NORD: PeeringDB fix list

AS214639 · peeringdb.com/net/40410

PeeringDB

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

Make the changes on ITM NORD's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.

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. Switzerland FogIXP Avers, Switzerland · PeeringDB 3756
    ProblemPeeringDB hasThe export has
    Port speed differs100G1G
    • In the entry with IPv6 2001:7f8:ca:1:0:21:4639:1: set Speed to 1000 (1G) (now 100000).

    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 ITM NORD has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Norway FIXO Oslo, Norway · PeeringDB 453Not on its website members list
    IPv491.198.176.126
    IPv6–
    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/214639/: 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.