ixreport

Telecom MPK: PeeringDB fix list

AS44927 · peeringdb.com/net/18918

PeeringDB

2 things to fix in Telecom MPK's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 18:53 UTC.

Make the changes on Telecom MPK'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 Telecom MPK'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.88
    IPv62a03:5f80:4::226:88
    Speed10000 Mbps (10G)
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

  2. Russia MSK-IX Moscow Moscow, Russia · PeeringDB 100From its IX-F export

    2 connections, so 2 entries:

    IPv4195.208.209.121
    IPv6–
    SpeedNot published
    RS peerYes
    IPv4195.208.211.35
    IPv6–
    SpeedNot published
    RS peerYes

    PeeringDB's IX-F import is on for this exchange, so PeeringDB also suggests this change on the network's PeeringDB page.

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