PAKT: PeeringDB fix list

AS39087 · peeringdb.com/net/2693

PeeringDB

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

Make the changes on PAKT'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 (1)

On the exchange's own member list, but not in PAKT's PeeringDB record. Add one entry per connection with these values.

  1. Sweden Netnod Stockholm GREEN -- MTU1500 Stockholm, Sweden · PeeringDB 70From its IX-F export
    IPv4194.68.123.121
    IPv62001:7f8:d:ff::121
    Speed5000000 Mbps (5T)
    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 BLUE -- MTU1500 Stockholm, Sweden · PeeringDB 2846
    ProblemPeeringDB hasThe export has
    Port speed differs20G5T
    • In the entry with IPv4 194.68.128.121: set Speed to 5000000 (5T) (now 20000).

Check these entries (1)

In PeeringDB, but on none of the exchange's own lists. If PAKT has left, delete the entry; if it's still connected, the exchange's list is wrong: ask the exchange to fix it.

  1. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100Not on its IX-F export
    IPv4195.208.209.49
    IPv62001:7f8:20:101::209:49
    Speed100000 Mbps (100G)
    IPv4195.208.210.49
    IPv62001:7f8:20:101::210:49
    Speed100000 Mbps (100G)

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