ixreport

American Data Networks: PeeringDB fix list

AS27876 · peeringdb.com/net/22477

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

Make the changes on American Data Networks'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.167200.107.83.167 200.107.83.190
    IPv6 address missing from PeeringDBnone2801:1d:a000:1::1190
    Port speed differs1G20G + 10G
    • In the entry with IPv4 200.107.83.167: set Speed to 20000 (20G) (now 1000).
    • Add an entry: IPv4 200.107.83.190, IPv6 2801:1d:a000:1::1190, speed 10000 (10G), 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/27876/: 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.