City of Sandy: PeeringDB fix list

AS32365 · peeringdb.com/net/4644

PeeringDB

One thing to fix in City of Sandy's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 20:58 UTC.

Make the changes on City of Sandy'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. United States NWAX Portland, United States · PeeringDB 165
    ProblemPeeringDB hasThe export has
    Port speed differs2 × 20G25G + 20G
    • In the entry with IPv4 198.32.195.57: set Speed to 25000 (25G) (now 20000).

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