ixreport

solytro_SOFIA: PeeringDB fix list

AS199400

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

AS199400 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 solytro_SOFIA's PeeringDB record. Add one entry per connection with these values.

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export

    4 connections, so 4 entries:

    IPv4178.18.236.115
    IPv62a03:5f80:4:2::236:115
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.236.152
    IPv62a03:5f80:4:2::236:152
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.236.199
    IPv62a03:5f80:4:2::236:199
    Speed10000 Mbps (10G)
    RS peerYes
    IPv4178.18.237.19
    IPv62a03:5f80:4:2::237:19
    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. Bulgaria TurkIX Sofia Sofia, Bulgaria · PeeringDB 4186From its IX-F export and website members list
    IPv4194.42.47.54
    IPv62001:7f8:161::54
    Speed100000 Mbps (100G)
    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/199400/: 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.