pCloud: PeeringDB fix list
AS51154 · peeringdb.com/net/24402
8 things to fix in pCloud's PeeringDB record, from what its exchanges publish: 1 to add, 7 to correct. As of 2026-10-08 21:56 UTC.
Make the changes on pCloud'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 pCloud's PeeringDB record. Add one entry per connection with these values.
-
The exchange's website members list doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
Correct these entries (7)
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 IPv6 address missing from PeeringDB none 2001:7f8::c7d2:0:1 - In the entry with IPv4 80.81.195.14: set IPv6 to 2001:7f8::c7d2:0:1 (now empty).
-
Problem PeeringDB has The export has IPv6 address missing from PeeringDB none 2001:7f8:16f::143 - In the entry with IPv4 195.60.85.143: set IPv6 to 2001:7f8:16f::143 (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 IPv6 address missing from PeeringDB none 2001:7f8:64:225:0:5:1154:1 - In the entry with IPv4 86.104.125.199: set IPv6 to 2001:7f8:64:225:0:5:1154:1 (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 IPv6 address missing from PeeringDB none 2001:67c:29f0::5:1154:1 2001:67c:29f0::5:1154:2 - In the entry with IPv4 185.1.226.13: set IPv6 to 2001:67c:29f0::5:1154:1 (now empty).
- In the entry with IPv4 185.1.226.7: set IPv6 to 2001:67c:29f0::5:1154:2 (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 IPv6 address missing from PeeringDB none 2001:7f8:14::ce:1 - In the entry with IPv4 91.210.17.53: set IPv6 to 2001:7f8:14::ce:1 (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 IPv6 address missing from PeeringDB none 2001:7f8:91::ce:1 - In the entry with IPv4 194.30.187.51: set IPv6 to 2001:7f8:91::ce:1 (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 IPv6 address missing from PeeringDB none 2001:7f8:13::a505:1154:1 - In the entry with IPv4 193.239.119.169: set IPv6 to 2001:7f8:13::a505:1154:1 (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.
From ixreport.com/net/51154/: 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.