Mobile 4G/5G Proxies

Mobile proxies route your traffic through real mobile carrier networks. The addresses belong to phone networks rather than to data centres or homes, which is why sites that are strict about residential and datacenter ranges often treat them differently.

You buy data, not proxies. Your plan is a number of gigabytes. Generating proxy lines costs nothing and is not limited by your balance, only your actual traffic draws it down. Generating ten thousand lines and using one of them consumes the same data as generating one.

One mobile account per BirdProxies account. Topping up adds gigabytes to the same account and keeps the same credentials, it does not create a second one.

Buying through a referral link adds 15% bonus data on top, applied automatically.

Five countries are available: Germany, United Kingdom, United States, Japan and Australia.

Behind them sit two different pools, and which one you get depends on the country you pick:

Australia runs on the general pool because the 4G/5G pool does not serve it. It works, it is simply a different set of carriers.

One country per request. If you need lines in two countries, generate twice.

Go to Mobile 4G/5G Proxies in your dashboard and set four things:

Lines come back as host:port:username:password, one per line. The dropdown above the output converts that to other shapes if your tool wants them differently, including a custom template with {host}, {port}, {username} and {password} placeholders.

Above 5,000 lines the result downloads as a text file instead of appearing on screen. Check your downloads folder rather than the output box.

TTL controls how long a sticky session keeps its IP. It runs from 5 minutes to 1 hour, and defaults to 1 hour if you do not set it. The slider sits behind the gear icon on the generation card.

There is no separate button that swaps your IP. To get a different address you either use rotating mode, wait for the sticky TTL to run out, or generate a fresh batch.

A password reset invalidates every line you have already generated. The moment it completes, previously issued proxies stop authenticating. Generate a new batch afterwards and replace whatever you had configured.

That is the point of the feature, so use it when credentials have leaked, not as a troubleshooting step.

20 generation requests per hour, counted per account across every route into it: the dashboard, the REST API and the MCP integration all draw from the same allowance. A request can ask for many thousands of lines, so this rarely bites unless something is looping.

Very large jobs are split into batches behind the scenes. If a batch fails partway you still receive the lines that succeeded, together with a warning saying how many you got. Read the count rather than assuming the full amount arrived.

Your balance may be shown from cache if our provider is briefly unreachable. The figure is then the last known one rather than live.