ixreport

itsoft_mow: PeeringDB fix list

AS48614

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

AS48614 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 itsoft_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.226.208
    IPv62a03:5f80:4::226:208
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.226.209
    IPv62a03:5f80:4::226:209
    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.210.65
    IPv62001:7f8:20:101::210:65
    SpeedNot published
    RS peerYes
    IPv4195.208.210.95
    IPv62001:7f8:20:101::210:95
    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/48614/: 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.