ixreport

IDNet: PeeringDB fix list

AS12496 · peeringdb.com/net/1108

PeeringDB

4 things to fix in IDNet's PeeringDB record, from what its exchanges publish: 2 to add, 2 to correct. As of 2026-10-08 22:13 UTC.

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

  1. Sweden Netnod Stockholm BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846From its IX-F export
    IPv4194.68.128.108
    IPv62001:7f8:d:fe::108
    Speed200000 Mbps (200G)
    RS peerYes
  2. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70From its IX-F export
    IPv4194.68.123.108
    IPv62001:7f8:d:ff::108
    Speed200000 Mbps (200G)
    RS peerYes

Correct these entries (2)

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. United Kingdom LINX LON1 London, United Kingdom · PeeringDB 18
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 195.66.224.181: set Speed to 100000 (100G) (now 30000).
  2. United Kingdom LINX LON2 London, United Kingdom · PeeringDB 321
    ProblemPeeringDB hasThe export has
    Port speed differs30G100G
    • In the entry with IPv4 195.66.236.181: set Speed to 100000 (100G) (now 30000).

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