Skip to content
DMA 104G MobileCA · San Francisco–Oakland–San Jose

San Francisco Bay Area mobile and residential proxies

DMA 807 covers SF, Oakland, San Jose, and the bulk of the Bay Area. Comcast-dominant residential + three-way mobile competition + disproportionate tech-product ad spend.

DMA rank
#10
City population
874k
Coordinates
37.775°, -122.419°
State
CA

San Francisco at a glance

San Francisco sits inside Nielsen DMA 10 (San Francisco–Oakland–San Jose). The metro's population is ~0.87M inside the city proper, with the DMA covering a larger surrounding area. Proxaro targets this metro specifically; you can reach it with X-PX-City: san-francisco or X-PX-Dma: 10 depending on whether you want tight city scope or full DMA rotation.

Tech products, developer tooling, SaaS creative, Bay Area DTC

SF / Bay Area is where tech-product ad creative, SaaS landing pages, and developer-tooling campaigns route their QA traffic by default. The Bay's network peers at Equinix SV1–SV10 (San Jose) and 1 Wilshire's northern reach; an SF-peered ASN announce is the signal the classifiers read as 'real Silicon Valley.' Useful for any creative targeting technical buyers or developer personas.

Carrier and ISP footprint

Residential coverage is available in addition to 4G and 5G mobile.

Targeting from the API

curl --proxy http://USER:PASS@gateway.proxaro.io:7777 \
     --proxy-header "X-PX-City: san-francisco" \
     --proxy-header "X-PX-State: california" \
     --proxy-header "X-PX-Carrier: t-mobile" \
     --proxy-header "X-PX-Session: sticky-20m" \
     https://example.com

Nearby markets

Parent state: California. Parent country: United States. See also the 4G mobile overview and residential overview.

Pricing

Pricing for San Francisco 4g mobile

San Francisco is covered on every paid plan. ASN pinning (e.g. T-Mobile) starts on the Carrier tier.

Plan
Local

$49/ mo

CoastMost popular

$149/ mo

Carrier

$449/ mo

Port

$799/ mo

Network

Custom

Bandwidth8 GB30 GB residential + 5 GB mobile80 GB residential + 30 GB 4G/5GUnmetered (500 GB fair use)Custom
Concurrent sessions100300600500Unlimited
RotationPer-request or 10-min stickyPer-request or sticky 1–60 minPer-request or sticky 1–60 minAPI-triggered; locked to one ASNPer-request or sticky 1–60 min
ProtocolsHTTP(S) + SOCKS5HTTP(S) + SOCKS5HTTP(S) + SOCKS5HTTP(S) + SOCKS5HTTP(S) + SOCKS5
GeotargetingState + top-20 DMAState + all 210 DMAsState + DMA + city + ASNState + DMA + city + ASNState + DMA + city + ASN
Carrier ASN pinningPool defaultPool defaultT-Mobile / Verizon / AT&T / Comcast / Spectrum / CoxDedicated carrierT-Mobile / Verizon / AT&T / Comcast / Spectrum / Cox
IPv6 supportOn 5G poolsOn 5G poolsOn 5G poolsOn 5G pools
SupportEmail (24h)Priority email + SlackDedicated Slack + phoneNamed engineerNamed engineer
Refund window7 days7 days7 days7 days7 days
Choose LocalChoose CoastChoose CarrierChoose PortChoose Network

FAQ

San Francisco 4G Mobile FAQ

  • How do I target San Francisco specifically on the API?
    Pass X-PX-City: san-francisco or X-PX-Dma: 10 in your request headers. State-level fallback via X-PX-State: ca.
  • What carriers dominate San Francisco 4g mobile?
    T-Mobile (AS21928), AT&T Mobility (AS20057), Verizon Wireless (AS22394) carry the bulk of San Francisco mobile traffic. Our pool rotation defaults to the largest carrier footprint unless you pin an ASN explicitly.
  • Can I hold a sticky session on a San Francisco exit?
    Up to 20 min in practice on San Francisco mobile. Sticky sessions survive within a single tower handover; cross-eNodeB movements may reassign.
  • How many exits are in San Francisco?
    We don't publish specific pool counts (they fluctuate daily), but San Francisco sits in the top-tier bucket on our network. Concurrency is ample.

Start routing San Francisco traffic through 4g mobile

Real ASNs, real edge capacity, and an engineer who answers your Slack the first time.