Volodymyr Puzanov: PeeringDB fix list
AS219458 · peeringdb.com/net/42657
One thing to fix in Volodymyr Puzanov's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-12 12:37 UTC.
Make the changes on Volodymyr Puzanov's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Add these exchanges (1)
On the exchange's own member list, but not in Volodymyr Puzanov's PeeringDB record. Add one entry per connection with these values.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64From its IX-F export and website members listIPv4 193.239.119.70 IPv6 2001:7f8:13::a521:9458:1 Speed Not published RS peer Yes PeeringDB's IX-F import is on for this exchange and this network allows automatic updates, so PeeringDB should make this change by itself. If it hasn't, PeeringDB may have hit a conflict: check the IX-F suggestions on the network's PeeringDB page.
From ixreport.com/net/219458/: 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.