Collecting data over AT&T Mobility: a technical guide

If a data pipeline needs to see the web the way an AT&T phone sees it, the cleanest route is to send requests out of an actual AT&T handset-class device. Each WeProx line is exactly that: a USB modem, router or Android phone with an AT&T SIM, located in one of our US metros, assigned to a single customer. You get host, port and credentials for HTTP(S) and SOCKS5, rotation by link or API, and unlimited data. This page covers the parts engineers ask about: verifying the exit, geolocation behavior, throughput planning and retry design.

Verify the exit before you trust the dataset

Build a verification step into the start of every crawl. Resolve the current public address through the proxy, then query an ASN and geolocation source. An AT&T line should report AS20057 with the organization AT&T Mobility LLC. Store that tuple alongside each batch: timestamp, exit IP, ASN, reported city. When a result looks odd weeks later, that metadata tells you instantly whether the network path was the variable.

Mobile IPv4 on AT&T sits behind carrier-grade NAT. The public address you see is shared by many subscribers in the same region, and it changes whenever the device reattaches. Treat the address as a session attribute, not a stable identifier, and key your logs on your own line ID instead.

Geolocation: what the databases will say

Carrier NAT pools are regional, so geolocation for mobile addresses is coarser than for fixed broadband. In our network the practical rules are simple. Miami and North Carolina lean AT&T, so those are the deepest AT&T pools we offer. AT&T lines served from our Boston site generally geolocate as New York rather than Boston, and Boston runs 4G LTE only. If your SERP or pricing study needs Boston specifically, use a Verizon line there instead.

For localized collection, sample a handful of geolocation providers once per rotation window and record their answers. Where they disagree, weight toward the one your target site is most likely to use. The goal is reproducibility: the same query from the same metro should land in the same bucket.

Throughput and concurrency planning

A single device is a single radio link, so capacity planning is about one line's bandwidth and latency rather than a pool of anonymous peers. Typical 4G throughput is around 20 to 45 Mbps; 5G, where AT&T offers its 5G+ service near the device, typically runs above 50 Mbps. Actual figures depend on signal at the site.

For HTML-heavy scraping the bottleneck is usually request latency, not bandwidth. A modest pool of concurrent connections per line, with keep-alive enabled, tends to outperform aggressive fan-out that triggers rate limiting on the target. Since data is unlimited on every plan, there is no reason to strip images or skip assets purely to save traffic; do it only if it speeds up parsing.

Rotation strategy for crawls

WeProx lines support sticky sessions, rotate on demand through a link or API, and a per-request mode. Rotations are unlimited, with no waiting period. For paginated crawls, stay sticky through a pagination chain so cursors and cookies line up, then rotate. For stateless endpoints, per-request rotation spreads load across the AT&T pool. Expect the same address to recur during a long day; the pool is finite, and deduplicating on content rather than on exit IP keeps your data clean.

Remember that platforms evaluate mobile traffic mainly on behavior, precisely because so many real users share each address. Respect robots directives and terms, keep request rates reasonable, and scrape public data you are entitled to collect.

Pricing for AT&T data lines

Every WeProx plan includes unlimited data, so cost scales with lines and time, not bytes. A 4G AT&T line is $4 per day, $26 per week or $60 per month. A 5G line is $6 per day, $32 per week or $75 per month. Pay by card, PayPal, crypto, Zelle or bank wire. If a project moves regions, relocate the line to another of our metros yourself at no cost, and support is available 24/7 over email and a Telegram bot.

AT&T proxy questions