California Mobile Proxy API: Los Angeles Lines From Code

A California line from Mobile Proxies US is a single SIM on AT&T, T-Mobile or Verizon in hardware we operate in Los Angeles, dedicated to one customer for the term. Developers reach it as an authenticated proxy on an HTTP(S) port and a SOCKS5 port, or through a VLESS tunnel, and manage it through the account API: list, rotate, status. This page covers how a Los Angeles address reads in geolocation, how the carriers behave there, the protocol and speed facts, and the price list.

Geolocation of a Los Angeles address

United States and California are reliable on every carrier. City resolution varies: T-Mobile addresses most often resolve to Los Angeles itself; AT&T is usually Los Angeles; Verizon's regional pools can place the address at a hub elsewhere in the West while the state remains California. Databases also lag each other after carriers re-plan their blocks, so two vendors can name two cities for one address.

Assert country, region, connection type (mobile) and carrier ASN in tests. Log the city. For a city-sensitive check, use T-Mobile and still log rather than fail.

Using the line from the API

GET /proxies/my returns the Los Angeles line with its uuid, carrier, network tier, expired_date, host, ports, authentication_user and rotation_link. Rotation is a plain GET on rotation_link, with no key; GET /proxy/status?license=UUID returns the current exit IP. Keep configuration keyed by licence uuid, which survives a free move between metros, re-read host and ports after a move, and never cache the exit IP for long.

Errors are JSON with a message field: a refused rotation is 400, and going over 300 requests per minute per account is 429 with a Retry-After header. /proxy/status returns 404 once a licence has expired.

Carriers in Los Angeles

All three carriers are present. T-Mobile for metro-accurate city readings and wide rotation pools; AT&T as a steady general choice; Verizon when a user report names it or when its regional geolocation is irrelevant to the job. Each line is one SIM, so for separate identities buy separate lines; a single line's HTTP and SOCKS5 ports share one address.

Los Angeles is a dense market with busy cells. Daytime speeds vary with cell load like any phone's; the up-to figures below are the plan's upper bounds.

Protocols, speeds and 5G+

HTTP(S) and SOCKS5 (with UDP) on every line; VLESS via the link on the line's dashboard page. 4G reads up to 25 Mbps download, 5G up to 50 Mbps. Devices: 4G/5G USB modem, cellular router or Android phone, chosen at checkout.

5G+ adds a higher average on selected 5G lines, 70 Mbps and above download, not guaranteed, for $2 a day, $5 a week, $15 a month or $45 per three months on top of a 5G plan. Not available on hourly plans.

Prices and plan rules

4G $5 a day, $29 a week, $66 a month; 5G $6 a day, $33 a week, $77 a month. Hourly: 4G $2 for two hours then $2 an hour, 5G $3 then $3 an hour, up to four hours, no auto-renewal, hours paid counting toward the day plan if you keep the line all day. Payment by card, PayPal, Bitcoin, USDT (incl. TRC-20), Ethereum, Zelle or bank wire. Activation is instant.

Data is not metered. The fair-use rule: a heavy day is 60 GB in one UTC day; heavy days are counted over the plan period; six are only logged; the seventh brings a warning in the dashboard, chat, email and bot; from the eighth the line is slowed to 20 Mbps until a clean UTC day passes; from the tenth it is held at 18 Mbps for the rest of the period.

What California lines are used for

Testing app and web flows as a California mobile user; checking state-specific pricing, privacy prompts and availability; reproducing Los Angeles user reports on the right carrier; measuring West Coast mobile latency to hosting regions; verifying your own ads, listings and store pages as they render in California. Your own accounts, within each platform's terms.

California proxy questions