milecom_15493: PeeringDB fix list

AS15493

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

AS15493 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 milecom_15493'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.151
    IPv62a03:5f80:4::225:151
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.225.196
    IPv62a03:5f80:4::225:196
    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 Ekaterinburg Ekaterinburg, Russia · PeeringDB 350From its IX-F export
    IPv4194.85.107.84
    IPv62001:7f8:20:301::107: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/15493/: 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.