Latin IP LLC: PeeringDB fix list
AS40731 · peeringdb.com/net/11551
One thing to fix in Latin IP LLC's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.
Make the changes on Latin IP LLC'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 (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 IPv6 address missing from PeeringDB none 2606:a980:0:7::6 IPv4 address in PeeringDB, not in the export 206.53.174.6 206.53.174.15 206.53.174.6 - The entry with IPv4 206.53.174.15, IPv6 – isn't in the export: delete it if that connection is gone.
- In the entry with IPv4 206.53.174.6: set IPv6 to 2606:a980:0:7::6 (now empty).
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/40731/: 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.