ixreport

CLARO ARGENTINA: PeeringDB fix list

AS11664 · peeringdb.com/net/2422

PeeringDB

2 things to fix in CLARO ARGENTINA's PeeringDB record, from what its exchanges publish: 1 to add, 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on CLARO ARGENTINA'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 CLARO ARGENTINA's PeeringDB record. Add one entry per connection with these values.

  1. Paraguay IXpy San Lorenzo, Paraguay · PeeringDB 1522From its IX-F export
    IPv4201.217.14.24
    IPv62001:1320:cafe::24
    Speed30000 Mbps (30G)
    RS peerYes

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.

  1. Paraguay IXpy San Lorenzo, Paraguay · PeeringDB 1522
    ProblemPeeringDB hasThe export has
    Address belongs to another network in PeeringDB201.217.14.24 is AS19037 AMX Argentina201.217.14.24
    Address belongs to another network in PeeringDB2001:1320:cafe::24 is AS19037 AMX Argentina2001:1320:cafe::24

    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.

From ixreport.com/net/11664/: 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.