Running Several US Mobile Proxy Lines Under One Account

One line is easy to run. The second line is where organisation starts to matter, and by the fifth most teams have lost track of which credentials belong to which client. This guide describes how a Mobile Proxies USA account is built for several lines at once: every line is its own SIM in its own device, with its own credentials, rotation link and renewal date, all listed in one dashboard at lines.mobileproxiesusa.com. Nothing here is a trick; it is the plain routine that keeps a fleet readable to the whole team.

What one account holds

An account is a container for lines. Each line you order is a separate device on our rack, with one carrier SIM in it, in one metro, assigned to you alone for the term you paid. The dashboard lists them as rows: carrier, metro, 4G or 5G, device type, term, renewal time, and the two things you actually use day to day, the proxy credentials and the rotation link. There is no shared pool behind the rows. If you hold ten lines, you hold ten modems or phones, and nobody else sends traffic through any of them.

Because each row is independent, each row can be different. A fleet can mix carriers (an AT&T line and a Verizon line in the same metro), mix metros (Chicago, Houston and Miami side by side), mix 4G and 5G, and mix terms (a monthly backbone with a few daily lines for a short campaign). The account is simply the list; the lines do not know about each other.

Name every line before anyone uses it

The dashboard lets you label each line. Use it the moment the line activates, before credentials are handed out. A label that works for teams carries three facts: who it serves, where it exits and what it is for. Something like client-northside, chicago, verizon, listings is enough. When a colleague later asks which line carries the Chicago listings for that client, the answer is in the row, not in someone's memory.

Keep the same labelling scheme across the whole fleet, and write the scheme down once in your own team notes. The scheme matters more than the specific words. A fleet where half the rows are labelled by client and half by city is harder to read than a fleet with no labels at all, because people trust the labels and stop checking.

Credentials per line, never shared across lines

Every line ships with its own username and password, a host, an HTTP port and a SOCKS5 port. Treat each set as belonging to exactly one line and exactly one purpose. The cleanest arrangement is one line per browser profile, one line per client workspace or one line per seat on the team. A line used by two people for two unrelated jobs at the same time behaves like a shared address, which is the thing you bought a dedicated line to avoid.

If a credential set has been pasted into too many places, reset it from the row. The reset is instant and only that line changes; the other rows keep working. Teams that onboard and offboard people regularly tend to reset the credentials of the lines that person touched as part of the offboarding checklist, the same way they would revoke a login.

Rotation links are per line too

Each row carries its own rotation link. Calling the link asks the carrier for a new address on that one SIM; the other lines are untouched. This is the main reason a fleet is more flexible than a single line with many profiles: you can rotate the address a client's work runs on without disturbing another client's sticky session on the next line over.

You can also set a timer per line from the row, rotate from the dashboard button, or leave a line alone. Left alone, the address stays as long as the carrier keeps it, which is usually hours and can be days. A new address is always from the same carrier in the same metro. Decide the rotation policy per line when you label it; write it into the label if the team needs to see it at a glance.

• Sticky lines: no timer, rotate only by hand when a job finishes.
• Scheduled lines: a timer in the row, for work that wants a fresh address every so often.
• Script-driven lines: the rotation link called from your own tooling between tasks.

Moving lines between metros without touching the others

A move is a self-service action on one row. Pick the new metro, confirm, and the line comes back in the new city with its remaining time preserved; the move is free. Credentials may change, so the row's label is what carries continuity. The other lines in the fleet are not affected, which means a team can shift one client's exit city for a regional campaign while the rest of the fleet stays where it was.

A move takes a little time because a device in the destination metro has to be assigned. Plan moves for the gap between tasks rather than in the middle of a sticky session, and update the proxy entry in the profile or tool that used the old row before anyone launches it again.

Renewals and the calendar

Every row has its own renewal time. A monthly line bought on the 3rd renews on the 3rd; a weekly line bought on a Tuesday renews on Tuesday. Auto-renew is per line and optional. For a fleet, the useful habit is to decide at purchase which lines are permanent and switch auto-renew on for those only, leaving campaign lines to expire on their own. The dashboard shows the next renewal per row, and the account balance can be topped up in advance so that renewals draw from it.

If a renewal is missed, the line keeps running for 24 hours, is then suspended for 24 hours with the device and SIM held for you, and is released back to stock at 48 hours. Nothing is pursued; the row simply disappears. For a team, this is a reason to keep one person responsible for the balance rather than letting each seat worry about it.

Who sees what on the team

Not everyone needs the dashboard. In most teams one or two people manage the fleet (ordering, labelling, moves, renewals) and the rest receive credentials for the lines they work on, usually by way of a profile browser workspace or a shared vault. That keeps the dashboard login narrow and makes the labels the single place where the mapping lives.

Support is per account, 24 hours a day, by email at [email protected] and through the Telegram bot at t.me/usamobileproxies_bot. When writing in about a line, quote the label or the host and port; a fleet owner with forty rows should not have to describe which one is misbehaving.

Frequently asked