Phoenix mobile and residential proxies — Cox's largest metro
DMA 753. Cox is the default Phoenix residential ISP — our Phoenix pool is the deepest Cox exposure in our network.
- DMA rank
- #12
- City population
- 1.61M
- Coordinates
- 33.448°, -112.074°
- State
- AZ
Phoenix at a glance
Phoenix sits inside Nielsen DMA 12 (Phoenix). The
metro's population is ~1.61M 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: phoenix or X-PX-Dma: 12 depending on
whether you want tight city scope or full DMA rotation.
Retail, solar, tourism, SaaS offices, retirees
Phoenix covers Maricopa County plus bits of Pinal. The metro's Cox AS22773 allocations announce from Equinix Phoenix PHX1–PHX2 and resolve cleanly to Maricopa ZIP codes. Phoenix is one of the fastest-growing US metros and hosts a distinctive residential-solar lead-gen market — AZ-IP rotations surface solar quote-flow and utility-rebate creative that out-of-state IPs never see.
Carrier and ISP footprint
- Mobile leaders: T-Mobile (AS21928), Verizon Wireless (AS22394), AT&T Mobility (AS20057).
- Residential ISPs: Cox (AS22773), CenturyLink (AS209).
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: phoenix" \
--proxy-header "X-PX-State: arizona" \
--proxy-header "X-PX-Carrier: t-mobile" \
--proxy-header "X-PX-Session: sticky-20m" \
https://example.com
Nearby markets
Parent state: Arizona. Parent country: United States. See also the 4G mobile overview and residential overview.
Pricing
Pricing for Phoenix residential
Phoenix 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 |
|---|---|---|---|---|---|
| Bandwidth | 8 GB | 30 GB residential + 5 GB mobile | 80 GB residential + 30 GB 4G/5G | Unmetered (500 GB fair use) | Custom |
| Concurrent sessions | 100 | 300 | 600 | 500 | Unlimited |
| Rotation | Per-request or 10-min sticky | Per-request or sticky 1–60 min | Per-request or sticky 1–60 min | API-triggered; locked to one ASN | Per-request or sticky 1–60 min |
| Protocols | HTTP(S) + SOCKS5 | HTTP(S) + SOCKS5 | HTTP(S) + SOCKS5 | HTTP(S) + SOCKS5 | HTTP(S) + SOCKS5 |
| Geotargeting | State + top-20 DMA | State + all 210 DMAs | State + DMA + city + ASN | State + DMA + city + ASN | State + DMA + city + ASN |
| Carrier ASN pinning | Pool default | Pool default | T-Mobile / Verizon / AT&T / Comcast / Spectrum / Cox | Dedicated carrier | T-Mobile / Verizon / AT&T / Comcast / Spectrum / Cox |
| IPv6 support | — | On 5G pools | On 5G pools | On 5G pools | On 5G pools |
| Support | Email (24h) | Priority email + Slack | Dedicated Slack + phone | Named engineer | Named engineer |
| Refund window | 7 days | 7 days | 7 days | 7 days | 7 days |
| Choose Local | Choose Coast | Choose Carrier | Choose Port | Choose Network |
FAQ
Phoenix Residential FAQ
How do I target Phoenix specifically on the API?
Pass X-PX-City: phoenix or X-PX-Dma: 12 in your request headers. State-level fallback via X-PX-State: az.What carriers dominate Phoenix residential?
T-Mobile (AS21928), Verizon Wireless (AS22394), AT&T Mobility (AS20057) carry the bulk of Phoenix 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 Phoenix exit?
Up to 60 min on Phoenix residential. For longer persistence, ISP is the better fit.How many exits are in Phoenix?
We don't publish specific pool counts (they fluctuate daily), but Phoenix sits in the top-tier bucket on our network. Concurrency is ample.
Start routing Phoenix traffic through residential
Real ASNs, real edge capacity, and an engineer who answers your Slack the first time.