ixreport

electron_moscow_mow: PeeringDB fix list

AS50911

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

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

Add these exchanges (2)

On the exchange's own member list, but not in electron_moscow_mow'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.221
    IPv62a03:5f80:4::226:221
    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
    IPv4195.208.209.84
    IPv62001:7f8:20:101::209:84
    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/50911/: 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.