infokom_SPB: PeeringDB fix list

AS48226

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

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

  1. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.225.229
    IPv62a03:5f80:4::225:229
    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/48226/: 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.