Sesameware: PeeringDB fix list

AS41268 · peeringdb.com/net/6061

PeeringDB

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

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.226.132
    IPv62a03:5f80:4::226:132
    Speed100000 Mbps (100G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export
    IPv4195.208.208.117
    IPv62001:7f8:20:101::208:117
    SpeedNot published
    RS peerYes

    PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.

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