NeoEdge: PeeringDB fix list
AS214232
One thing to fix in NeoEdge's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 18:53 UTC.
AS214232 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 NeoEdge's PeeringDB record. Add one entry per connection with these values.
-
nine Amsterdam, Bordeaux, Frankfurt, Genève, Lille, London, Lyon, Marseille, Milano, Montpellier, Paris, Zurich, France · PeeringDB 4705From its IX-F export
IPv4 185.1.14.170 IPv6 2001:7f8:12e::21:4232:1 Speed 10000 Mbps (10G) RS peer Yes 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/214232/: 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.