ixreport

fexnet: PeeringDB fix list

AS42913

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

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

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

    The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.

    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/42913/: 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.