ixreport

Tigo Costa Rica: PeeringDB fix list

AS262197 · peeringdb.com/net/30007

One thing to fix in Tigo Costa Rica's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 UTC.

Make the changes on Tigo Costa Rica'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.

  1. Costa Rica CRIX San Jose, Costa Rica · PeeringDB 1023
    ProblemPeeringDB hasThe export has
    IPv4 address missing from PeeringDB200.107.83.188200.107.83.188 200.107.83.189
    IPv6 address missing from PeeringDB2801:1d:a000:1::11882801:1d:a000:1::1188 2801:1d:a000:1::1189
    Port speed differs50G2 × 50G
    • Add an entry: IPv4 200.107.83.189, IPv6 2801:1d:a000:1::1189, speed 50000 (50G), 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/262197/: 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.