Fouredge: PeeringDB fix list

AS48220 · peeringdb.com/net/20943

PeeringDB

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

Make the changes on Fouredge'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 Fouredge'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.129
    IPv62001:7f8:d:fb::129
    SpeedNot published
    RS peerYes
  2. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845From its IX-F export
    IPv4195.245.240.129
    IPv62001:7f8:d:fc::129
    SpeedNot published
    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 Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:7f8:d:ff::129
    • In the entry with IPv4 194.68.123.129: set IPv6 to 2001:7f8:d:ff::129 (now empty).

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