ANTEL: PeeringDB fix list

AS6057 · peeringdb.com/net/1495

PeeringDB

4 things to fix in ANTEL's PeeringDB record, from what its exchanges publish: 1 to add, 3 to correct. As of 2026-10-08 20:58 UTC.

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

  1. Paraguay IXpy San Lorenzo, Paraguay · PeeringDB 1522From its IX-F export and website members list
    IPv4201.217.14.45
    IPv62001:1320:cafe::45
    Speed1000 Mbps (1G)
    RS peerYes

Correct these entries (3)

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. Germany DE-CIX Frankfurt Frankfurt, Germany · PeeringDB 31
    ProblemPeeringDB hasThe export has
    Port speed differs10G100G
    • In the entry with IPv4 80.81.195.175: set Speed to 100000 (100G) (now 10000).
  2. France DE-CIX Marseille Marseille, France · PeeringDB 1149
    ProblemPeeringDB hasThe export has
    Port speed differs3G10G
    • In the entry with IPv4 185.1.47.16: set Speed to 10000 (10G) (now 3000).
  3. South Africa NAPAfrica IX Johannesburg Johannesburg, South Africa · PeeringDB 592
    ProblemPeeringDB hasThe export has
    Port speed differs200M10G
    • In the entry with IPv4 196.60.10.218: set Speed to 10000 (10G) (now 200).

    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/6057/: 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.