IPONE: PeeringDB fix list
AS58141 · peeringdb.com/net/39975
One thing to fix in IPONE's PeeringDB record, from what its exchanges publish: 1 to add. As of 2026-10-08 22:13 UTC.
Make the changes on IPONE'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 IPONE'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 list2 connections, so 2 entries:
IPv4 193.239.118.85 IPv6 2001:7f8:13::a505:8141:2 Speed Not published RS peer Yes IPv4 193.239.119.150 IPv6 2001:7f8:13::a505:8141:1 Speed Not published 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/58141/: 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.