Plug an AT&T mobile exit into your automation stack

Automation lives or dies on predictable infrastructure. A NeonProxies AT&T line gives your workers one fixed endpoint that fronts a real AT&T device, a USB modem, router or Android phone running its own SIM in a US metro, reserved for your account. Credentials never change, rotation is a single HTTP call, and there is no data meter for your scheduler to worry about. This page is written for the people who build the bots: how to treat the line as a resource in code, how to structure rotation inside job queues, and what the AT&T network looks like to the services on the other end.

Model the line as a resource, not an IP

The mistake we see most often is hard-coding an exit address into config. On a mobile line the public address is ephemeral by design; the stable thing is the endpoint. Store host, port, username and password from the dashboard as a named resource, something like att-mia-01, and let every worker reference that name. When the address changes after a rotation, nothing in your fleet needs to know.

Pick the transport that fits each worker. HTTP(S) proxying suits API clients and simple fetchers. SOCKS5 suits browser automation and anything that opens raw sockets, and UDP over SOCKS5 is available for tools that need datagrams. Both ports sit in front of the same AT&T device, so they share its current address.

Rotation as a job-queue primitive

Each line exposes a rotation link you can hit with a plain GET, and the same action is available through the API. There is no limit on rotations and no minimum gap between them. That makes rotation easy to treat as a step in a workflow rather than a manual chore.

A pattern that works well: give the line a mutex in your queue. A worker acquires it, runs its unit of work in sticky mode, calls rotate, waits for the new address to answer a health probe, then releases. For stateless fan-out, switch the line to per-request mode and skip the lock entirely. Log the address before and after each rotation so you can spot repeats; AT&T serves each region from a finite carrier NAT pool, and seeing an address again within a day is normal.

• acquire lock, run task batch on sticky session
• call the rotation endpoint
• poll a lightweight IP echo until the address differs, with a short timeout
• record old and new address, release lock

What the target sees

From the outside, your traffic resolves to AS20057, AT&T Mobility LLC, the same network every AT&T phone on cellular data uses. There is no hosting ASN, no datacenter reverse DNS, no proxy flag in the registry, because the packets really do leave through an AT&T radio.

AT&T multiplexes subscribers through carrier-grade NAT, so a single public address may front many ordinary users. That is why modern anti-abuse systems score mobile traffic mostly on behavior. Your bot's timing, header consistency and session hygiene will matter far more than the address. Build polite automation: sane concurrency, jittered delays, respect for rate limits and terms of service. Use it for legitimate jobs such as monitoring, testing, reporting and operating accounts you are authorized to run.

Placement: Miami, North Carolina and the Boston caveat

Carrier and hardware type are chosen at checkout and depend on stock per metro. For AT&T, Miami and North Carolina are our strongest sites. AT&T also appears in New York, Los Angeles, Chicago, Houston, Phoenix and Boston when devices are available.

If your automation keys off geolocation, note that AT&T addresses served from Boston usually resolve to New York in the common databases, and Boston is LTE only. Need a Boston tag? Use Verizon there. Moving a line between metros is free and self-service from the dashboard, and your worker config does not change because the endpoint stays the same.

Throughput and cost for always-on workers

On 4G, expect roughly 20 to 45 Mbps; on 5G, where AT&T's 5G+ reaches the device, typically above 50 Mbps. Signal at the site sets the real ceiling. For headless browser farms rendering heavy pages, 5G reduces wall-clock time; for API polling, 4G is usually plenty.

Plans are flat and include unlimited data. A 4G AT&T line is $5 per day, $30 per week or $68 per month; 5G is $7 per day, $35 per week or $82 per month. Pay by card through Stripe, PayPal, Bitcoin, USDT, Ethereum, Zelle or bank wire. Support runs 24/7 by email and through our Telegram bot, staffed by people who understand modems and automation.

AT&T proxy questions