ixreport

Alcom: PeeringDB fix list

AS3238 · peeringdb.com/net/3068

PeeringDB

4 things to fix in Alcom's PeeringDB record, from what its exchanges publish: 4 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Alcom'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 (4)

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 BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs100G40T
    • In the entry with IPv4 194.68.128.135: set Speed to 40000000 (40T) (now 100000).
  2. Sweden Netnod Stockholm BLUE -- MTU4470 Stockholm, Sweden · PeeringDB 2847
    ProblemPeeringDB hasThe export has
    Port speed differs100G40T
    • In the entry with IPv4 195.69.119.135: set Speed to 40000000 (40T) (now 100000).
  3. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70
    ProblemPeeringDB hasThe export has
    Port speed differs100G40T
    • In the entry with IPv4 194.68.123.135: set Speed to 40000000 (40T) (now 100000).
  4. Sweden Netnod Stockholm GREEN -- MTU4470 Stockholm, Sweden · PeeringDB 2845
    ProblemPeeringDB hasThe export has
    Port speed differs100G40T
    • In the entry with IPv4 195.245.240.135: set Speed to 40000000 (40T) (now 100000).

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