ixreport

Ridge Wireless

AS33452

3Exchanges
0On an exchange's list, not in PeeringDB
0In PeeringDB, not on the exchange's list
Cable/DSL/ISPType
OpenPeering policy
0Using the route servers
1To fix in PeeringDB
3Facilities in PeeringDB

Tools: Where can I peer with Ridge Wireless? · Where should Ridge Wireless peer next? · Compare Ridge Wireless with another network

This network elsewhere: its registry history on RIR Tracker · its routes on BGP Report

PeeringDB fix list Printable page · CSV

One thing to fix in Ridge Wireless's PeeringDB record, from what its exchanges publish: 1 to correct. As of 2026-11-19 12:40 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).

Exchanges over time

0123Oct 3, 2026Nov 19, 20263
Show as a table
DateExchanges
Nov 19, 20263
Nov 18, 20263
Nov 17, 20263
Nov 16, 20263
Nov 15, 20263
Nov 14, 20263
Nov 13, 20263
Nov 12, 20263
Nov 11, 20263
Nov 10, 20263
Nov 9, 20263
Nov 8, 20263
Nov 7, 20263
Nov 6, 20263
Nov 5, 20263
Nov 4, 20263
Nov 3, 20263
Nov 2, 20263
Nov 1, 20263
Oct 31, 20263
Oct 30, 20263
Oct 29, 20263
Oct 28, 20263
Oct 27, 20263
Oct 26, 20263
Oct 25, 20263
Oct 24, 20263
Oct 23, 20263
Oct 22, 20263
Oct 21, 20263
Oct 20, 20263
Oct 19, 20263
Oct 18, 20263
Oct 17, 20263
Oct 16, 20263
Oct 15, 20263
Oct 14, 20263
Oct 13, 20263
Oct 12, 20263
Oct 11, 20263
Oct 10, 20263
Oct 9, 20263
Oct 8, 20263
Oct 7, 20263
Oct 6, 20263
Oct 5, 20263
Oct 4, 20263
Oct 3, 20263

Map

Where Ridge Wireless's exchanges are, colored by how PeeringDB and each exchange's own list compare, and the buildings it lists in PeeringDB, marked where it could peer on an exchange it isn't on yet.

Exchanges

Total port capacity 21G across 3 exchanges.

United States Any2West Los Angeles and Silicon Valley, United States 206.72.211.215 10G PeeringDB
United States FCIX Fremont, United States 206.80.238.31 1G Both
United States SFMIX San Francisco, United States 206.197.187.47 10G Both IPv6 not in PeeringDB

Exchanges in its buildings that it isn't on (10)

These exchanges have a switch in a facility where Ridge Wireless lists itself in PeeringDB, but don't have Ridge Wireless as a member in PeeringDB, their IX-F export or their website. Joining one is usually just a cross-connect away. The biggest exchanges come first; ghost exchanges are left out.

United States EVIXFremont, United States 227 Hurricane Electric Fremont 2
United States FREMIXFremont, United States 141 Hurricane Electric Fremont 2
Puerto Rico PR-IXSan Juan, Puerto Rico 33 Hurricane Electric Fremont 2
United States ARIXFremont, Portland, Flagstaff, United States 22 Hurricane Electric Fremont 2
United States Lambda-IXFremont, United States 22 Hurricane Electric Fremont 2
United States MegaIX Bay AreaSan Francisco, United States 21 CoreSite - San Jose (SV1); Hurricane Electric Fremont 2
United States Zero Internet eXchange San JoseSan Jose, United States 15 Hurricane Electric Fremont 2
United States DACS-IX WestSilicon Valley, United States 14 Hurricane Electric Fremont 2
United States Ninja-IX Bay AreaNorthern California, United States 6 Hurricane Electric Fremont 2
Australia ixFabricGlobal, Australia 2 Hurricane Electric Fremont 2
Facilities (3)

The buildings Ridge Wireless lists in PeeringDB, and how many of the exchanges in each it's on.

United States Hurricane Electric Fremont 2Fremont 2 of 12
United States CoreSite - San Jose (SV1)San Jose 2 of 3
United States Evocative SJC3Santa Clara No exchange