NETCLOUDIFY SLU: PeeringDB fix list
AS216392 · peeringdb.com/net/39111
2 things to fix in NETCLOUDIFY SLU's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 20:58 UTC.
Make the changes on NETCLOUDIFY SLU'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 NETCLOUDIFY SLU's PeeringDB record. Add one entry per connection with these values.
-
IPv4 185.1.192.229 IPv6 2001:7f8:a0:0:3:4d48:0:1 Speed 1000 Mbps (1G) RS peer Yes
Correct these entries (1)
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 Port speed differs 10G 2G - In the entry with IPv4 193.242.98.174: set Speed to 2000 (2G) (now 10000).
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/216392/: 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.