ixreport

M2 CONNECT LLC: PeeringDB fix list

AS56814 · peeringdb.com/net/36837

PeeringDB

2 things to fix in M2 CONNECT LLC's PeeringDB record, from what its exchanges publish: 2 to add. As of 2026-10-08 22:13 UTC.

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    2 connections, so 2 entries:

    IPv4178.18.225.78
    IPv62a03:5f80:4::225:78
    Speed100000 Mbps (100G)
    RS peerYes
    IPv4178.18.224.52
    IPv62a03:5f80:4::224:52
    Speed100000 Mbps (100G)
    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.208.191
    IPv62001:7f8:20:101::208:191
    SpeedNot published
    RS peerYes
    IPv4195.208.210.105
    IPv62001:7f8:20:101::210:105
    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/56814/: 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.