ixreport

Ridge Wireless: PeeringDB fix list

AS33452 · peeringdb.com/net/15932

PeeringDB

One thing to fix in Ridge Wireless's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-10-08 18:53 UTC.

Make the changes on Ridge Wireless'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 SFMIX San Francisco, United States · PeeringDB 155
    ProblemPeeringDB hasThe export has
    IPv6 address missing from PeeringDBnone2001:504:30::ba03:3452:1
    • In the entry with IPv4 206.197.187.47: set IPv6 to 2001:504:30::ba03:3452:1 (now empty).

From ixreport.com/net/33452/: 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.