Ufinet Latam AS52468: PeeringDB fix list
AS52468 · peeringdb.com/net/13873
2 things to fix in Ufinet Latam AS52468's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 22:13 UTC.
Make the changes on Ufinet Latam AS52468'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 Ufinet Latam AS52468's PeeringDB record. Add one entry per connection with these values.
-
The exchange's IX-F export doesn't give addresses or a speed. Use the addresses on your router, or ask the exchange.
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 Address belongs to another network in PeeringDB 201.217.14.23 is AS264853 Ufinet Paraguay 201.217.14.23 Address belongs to another network in PeeringDB 2001:1320:cafe::23 is AS264853 Ufinet Paraguay 2001:1320:cafe::23 IPv4 address in PeeringDB, not in the export 201.217.14.0 201.217.14.23 IPv6 address in PeeringDB, not in the export 2001:1320:cafe:: 2001:1320:cafe::23 Port speed differs 1G 10G An address another network has in PeeringDB isn't suggested here: either that network's entry or the exchange's export is wrong. Ask the exchange which.
- In the entry with IPv4 201.217.14.0: set IPv4 to (empty) (now 201.217.14.0); set IPv6 to (empty) (now 2001:1320:cafe::); set Speed to 10000 (10G) (now 1000).
From ixreport.com/net/52468/: 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.