Firebase Mobile Proxies: Auth, App Check and Hosting From the US
Firebase sits under a large share of mobile apps, and several of its services make decisions at the client: phone Auth and its reCAPTCHA or Play Integrity checks, App Check attestation, Remote Config conditions keyed on country, Hosting and Cloud Functions latency from the user's network. Testing those from a laptop in the office or a cloud box misses the US mobile case. A Mobile Proxies US line is that case: one carrier SIM in one US metro, HTTP(S), SOCKS5 and VLESS endpoints, exit IP and rotation in an API.
Client-side Firebase behaviour that depends on the network
Phone Auth: the verification path (reCAPTCHA on web, Play Integrity or APNs on native) and the SMS send both weigh the source address; hosting ASNs get more friction. App Check: attestation providers look at device and environment, and the backend policy may consider the request's origin. Remote Config: conditions on country and region evaluate against the client's apparent location. Hosting, Firestore and Functions: latency and connection behaviour under cellular conditions.
Server-side Admin SDK calls and CI deployments are unaffected and stay on your normal addresses.
Testing phone Auth and OTP from a US carrier address
Run your web app in a browser profile behind the line's HTTP endpoint, or your Android build in an emulator behind the SOCKS5 endpoint so Play services traffic and DNS follow the line. Trigger phone sign-in with your own test numbers. Observe how often reCAPTCHA appears, whether invisible verification passes, and how long the SMS takes. Compare across carriers by buying one line per carrier.
Use Firebase's test phone numbers for automated runs so no SMS is sent; use a real number you own for a manual end-to-end pass. Record exit IP and carrier from the API per attempt.
Remote Config, Hosting and Functions by region
Remote Config conditions on country resolve from the client's address. A line in Miami evaluates as a US client; a free move to Phoenix is still US but a different metro, useful when conditions key on region or when you compare Hosting edge latency. Time Firestore reads and Functions calls from the line to measure what a US mobile user waits.
A 4G line (up to 25 Mbps download) represents a typical user; a 5G line (up to 50 Mbps) the better case. Data is not metered on either.
Debug tokens, SMS regions and country conditions
App Check will not attest a plain emulator, so use the debug provider and register its token in the console for that build; the line then supplies the network and the debug token supplies the attestation. Keep these runs labelled, since they exercise your enforcement path and not Play Integrity itself.
The SMS region policy on Identity Platform allows or denies destinations by country code, which depends on the phone number rather than the client address. Test both axes on purpose: a US number from the line, then the same number from your office, and note which step changed.
For Remote Config country conditions, sim_location in GET /proxies/my tells you where the address shows now, so a surprising value can be checked at once. Confirm with a second address by calling rotation_link and repeating the fetch once the minimum fetch interval in your app allows it.
Rotation and terms
Rotate between runs by API and confirm the new exit IP first. Rotate during a Firestore realtime listener on purpose to test reconnection against a genuine carrier re-attach.
Use your own Firebase project, test accounts and test numbers within Google's terms. The line is the US mobile client position for your own app; it does not alter project quotas or regions.
Setting up a Firebase proxy on Mobile Proxies US
- Buy a line on the carrier you want to test; one per carrier for comparisons.
- Read endpoints from the API and configure the emulator (SOCKS5) or browser profile (HTTP).
- Confirm the exit IP is a carrier address and matches ip from GET /proxy/status.
- Run phone Auth, App Check, Remote Config and latency checks; log exit IP, carrier and timings per case.
- Rotate between runs; rotate mid-listener to test Firestore and Realtime Database reconnects.
Firebase proxy questions
Will Play Integrity pass in an emulator behind the line?
Integrity depends on the device and Play services, not the proxy. Use a test device with Wi-Fi proxy set to the line for integrity checks; the emulator is fine for everything else.
Should the Admin SDK go through the line?
No. Server-side calls stay on your server. The line represents the end user.
Does Remote Config see the line as a US client?
Yes. The address belongs to a US carrier and geolocates to the US and to the line's state; metro-level accuracy is best on T-Mobile.