ixreport

g-service_mow: PeeringDB fix list

AS33991

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

AS33991 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 g-service_mow'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.94
    IPv62a03:5f80:4::225:94
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.227.92
    IPv62a03:5f80:4::227:92
    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 Novosibirsk Novosibirsk, Russia · PeeringDB 223From its IX-F export
    IPv4193.232.87.88
    IPv62001:7f8:20:401::87:88
    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/33991/: 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.