MarbleISL Network: PeeringDB fix list
AS213092 · peeringdb.com/net/23561
5 things to fix in MarbleISL Network's PeeringDB record, from what its exchanges publish: 5 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on MarbleISL Network's PeeringDB page: sign in, choose Edit, and find the exchanges under Public Peering Exchange Points. Speeds go in as megabits per second.
Correct these entries (5)
Addresses or port speeds in PeeringDB that differ from the exchange's IX-F export. The changes below follow the export; if the export is the one that's wrong, tell the exchange instead.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 185.1.170.243 IPv6 address in PeeringDB, not in the export 2001:7f8:9e:0:3:406:0:1 2001:7f8:9e:0:3:4064:0:1 2001:7f8:9e:0:3:406:0:1 Port speed differs 200G + 1G 200G - The entry with IPv4 –, IPv6 2001:7f8:9e:0:3:4064:0:1 isn't in the export: delete it if that connection is gone.
- In the entry with IPv6 2001:7f8:9e:0:3:406:0:1: set IPv4 to 185.1.170.243 (now empty).
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 193.189.83.83 - In the entry with IPv6 2001:7f8:33::a121:3092:1: set IPv4 to 193.189.83.83 (now empty).
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.
-
NL-ix Amsterdam, Rotterdam, Brussels, Luxembourg, Frankfurt, Düsseldorf, Berlin, Dublin, London, Copenhagen, Paris, Marseille, Netherlands · PeeringDB 64Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 193.239.119.129 - In the entry with IPv6 2001:7f8:13::a521:3092:1: set IPv4 to 193.239.119.129 (now empty).
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 149.112.50.62 - In the entry with IPv6 2001:504:125:e1::62: set IPv4 to 149.112.50.62 (now empty).
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.
-
Problem PeeringDB has The export has IPv4 address missing from PeeringDB none 192.34.27.32 - Add an entry: IPv4 192.34.27.32, IPv6 –.
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/213092/: 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.