cloud4y_MSK: PeeringDB fix list

AS203714

One thing to fix in cloud4y_MSK's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 20:58 UTC.

AS203714 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.

Add these exchanges (1)

On the exchange's own member list, but not in cloud4y_MSK'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.224.120
    IPv62a03:5f80:4::224:120
    Speed20000 Mbps (20G)
    RS peerYes
    IPv4178.18.224.210
    IPv62a03:5f80:4::224:210
    Speed20000 Mbps (20G)
    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/203714/: 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.