LACNIC: PeeringDB fix list
AS52224
4 things to fix in LACNIC's PeeringDB record, from what its exchanges publish: 4 to add. As of 2026-10-08 20:58 UTC.
AS52224 has no PeeringDB record. Create one (register, then request the network for your organisation) before adding these exchanges.
Add these exchanges (4)
On the exchange's own member list, but not in LACNIC's PeeringDB record. Add one entry per connection with these values.
-
2 connections, so 2 entries:
IPv4 179.0.201.201 IPv6 2801:17:c000:201::201 Speed 1000 Mbps (1G) RS peer Yes IPv4 179.0.201.200 IPv6 2801:17:c000:201::200 Speed 1000 Mbps (1G) 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.
-
IPv4 201.217.14.110 IPv6 2001:1320:cafe::110 Speed 1000 Mbps (1G) RS peer Yes -
4 connections, so 4 entries:
IPv4 45.68.88.3 IPv6 – Speed 1000 Mbps (1G) RS peer Yes IPv4 – IPv6 2801:18d::3 Speed 1000 Mbps (1G) RS peer Yes IPv4 – IPv6 2801:18d::4 Speed 1000 Mbps (1G) RS peer Yes IPv4 45.68.88.4 IPv6 – Speed 1000 Mbps (1G) 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.
-
2 connections, so 2 entries:
IPv4 45.68.40.250 IPv6 2801:1f5::250 Speed 10000 Mbps (10G) RS peer Yes IPv4 45.68.40.251 IPv6 2801:1f5::251 Speed 10000 Mbps (10G) 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/52224/: 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.