ixreport

CRIX Route Servers: PeeringDB fix list

AS52385 · peeringdb.com/net/11529

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

Make the changes on CRIX Route Servers'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
    Port speed differs2 × 100G2 × 10M
    • In the entry with IPv4 200.107.83.129: set Speed to 10 (10M) (now 100000).
    • In the entry with IPv4 200.107.83.130: set Speed to 10 (10M) (now 100000).

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