ixreport

atom3_waw: PeeringDB fix list

AS208846

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

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

  1. Poland 1-IX EU New-York, London, Paris, Madrid, Frankfurt, Amsterdam, Warsaw, Bratislava, Hong Kong, Poland · PeeringDB 3958From its website members list

    The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

  2. Netherlands GNM-IX Amsterdam, Netherlands · PeeringDB 358From its IX-F export
    IPv4178.18.237.22
    IPv62a03:5f80:4:2::237:22
    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/208846/: 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.