ixreport

bitbynet_MSK: PeeringDB fix list

AS52094

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

AS52094 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 bitbynet_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.4
    IPv62a03:5f80:4::224:4
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.226.228
    IPv62a03:5f80:4::226:228
    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.

From ixreport.com/net/52094/: 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.