RETN: PeeringDB fix list

AS9002 · peeringdb.com/net/124

PeeringDB

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

Make the changes on RETN'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 RETN'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.157
    IPv62001:7f8:d:fb::157
    SpeedNot published
    RS peerNo
  2. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.157
    IPv62001:7f8:d:fc::157
    SpeedNot published
    RS peerNo

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB80.81.192.7380.81.192.73 80.81.193.181
    IPv6 address missing from PeeringDB2001:7f8::232a:0:12001:7f8::232a:0:1 2001:7f8::5f6d:0:3
    Port speed differs200G800G + 200G
    • Add an entry: IPv4 80.81.193.181, IPv6 2001:7f8::5f6d:0:3, speed 800000 (800G), RS peer yes.
  2. Italy MIX-IT Milan, Italy · PeeringDB 35
    ProblemPeeringDB hasThe export has
    Port speed differs200G2 × 200G
    • Add an entry: IPv4 217.29.66.116, IPv6 –, speed 200000 (200G), RS peer no.

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