Kansas City mobile and residential proxies — DMA 616
Bi-state metro. T-Mobile's legacy Sprint HQ is in Overland Park, KS right across the border.
- DMA rank
- #33
- City population
- 508k
- Coordinates
- 39.100°, -94.579°
- State
- MO
Kansas City at a glance
Kansas City sits inside Nielsen DMA 33 (Kansas City). The
metro's population is ~0.51M 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: kansas-city or X-PX-Dma: 33 depending on
whether you want tight city scope or full DMA rotation.
Logistics, fintech (Commerce / UMB), BBQ retail
Kansas City straddles MO + KS; the Kansas side (Overland Park, Shawnee, Leawood) is where Sprint HQ'd and T-Mobile now operates the legacy Sprint campus. That gives KC an unusually dense T-Mobile footprint. KC's logistics ecosystem (Union Pacific, BNSF, major e-commerce fulfillment) drives a disproportionate share of the metro's B2B advertising.
Carrier and ISP footprint
- Mobile leaders: T-Mobile (AS21928), AT&T Mobility (AS20057), Verizon Wireless (AS22394).
- Residential ISPs: Spectrum (AS20115), AT&T Internet (AS7018).
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: kansas-city" \
--proxy-header "X-PX-State: missouri" \
--proxy-header "X-PX-Carrier: t-mobile" \
--proxy-header "X-PX-Session: sticky-20m" \
https://example.com
Nearby markets
Parent state: Missouri. Parent country: United States. See also the 4G mobile overview and residential overview.
Pricing
Pricing for Kansas City 5g mobile
Kansas City 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
Kansas City 5G Mobile FAQ
How do I target Kansas City specifically on the API?
Pass X-PX-City: kansas-city or X-PX-Dma: 33 in your request headers. State-level fallback via X-PX-State: mo.What carriers dominate Kansas City 5g mobile?
T-Mobile (AS21928), AT&T Mobility (AS20057), Verizon Wireless (AS22394) carry the bulk of Kansas City 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 Kansas City exit?
Up to 20 min in practice on Kansas City mobile. Sticky sessions survive within a single tower handover; cross-eNodeB movements may reassign.How many exits are in Kansas City?
We don't publish specific pool counts (they fluctuate daily), but Kansas City sits in the mid-tier bucket on our network. Concurrency is live but moderate; plan rotation accordingly.
Start routing Kansas City traffic through 5g mobile
Real ASNs, real edge capacity, and an engineer who answers your Slack the first time.