Bel Air Internet: PeeringDB fix list

AS23316 · peeringdb.com/net/4274

PeeringDB

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

Make the changes on Bel Air Internet'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
    IPv6 address missing from PeeringDBnone2620:124:2000::145
    • In the entry with IPv4 198.32.195.145: set IPv6 to 2620:124:2000::145 (now empty).

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