Residential Proxies for iPhone & Shadowrocket

What is Shadowrocket on iPhone, and why put a proxy in it?

An iPhone can send all of its traffic — apps included — through a proxy, either with the built-in HTTP proxy setting on a Wi-Fi network or with a client such as Shadowrocket, Potatso or Quantumult X that supports SOCKS5 and HTTP with authentication and works on cellular too. That is what social-media managers use to run an account from the phone as if it were in the client's country, what QA teams use to test apps as users abroad, what streaming and ad-verification teams use to check what an app shows in a market, and what travellers use to keep a stable network identity at home. The proxy has to be one the client can authenticate to and one that looks like a phone: a mobile or residential exit with username and password, held on a sticky session.

Why residential proxies for iPhone and Shadowrocket

For QA and verification at lower cost, a residential exit through the same client gives the phone a home-ISP address in the target country from $1.00/GB down to $0.80; Premium sticky sessions last up to 24 hours. Use it for testing and checks, mobile for accounts.

What a proxy does not do. A proxy changes the network the phone's traffic leaves from; it does not change the Apple ID's region, the App Store country, or the SIM's country, which some apps also read. Apps' and platforms' terms apply to what you do through the proxy. Carrier IPs for the same job are on the mobile proxies for iPhone and Shadowrocket page.

Best residential proxies for iPhone and Shadowrocket

Shadowrocket holds one proxy configuration for the whole device, so one sticky exit per phone, with a lifetime long enough for the day. The exit country matches the accounts used on that phone. With QuanticData the exits asked for most are the United States, the United Kingdom and the United Arab Emirates, with state and city targeting in the username at no extra cost.

Everything the phone does goes through the proxy, so bandwidth is that of the apps used — light for messaging, heavy for video. On the residential network that means Residential Basic for rotating exits and sessions of up to 120 minutes, Premium for sessions of up to 24 hours, from $1.00/GB with a free 100 MB trial. For iPhone and Shadowrocket the residential network is the usual choice: the phone needs one stable exit with a long session, which Residential Premium provides at a lower price per GB, and a home-ISP exit in the right country is what that needs.

How to start with iPhone and Shadowrocket in minutes

1. Create a free QuanticData account and open Plans → Residential; pick a bundle — $1.00/GB is enough to test iPhone and Shadowrocket on your real workflow.
2. Copy host, port, username and password from the dashboard. Put the country in the username (-country-us), and state or city if the job is local (-region-…-city-…), and a session ID with a lifetime when the iPhone and Shadowrocket flow must keep one IP.
3. In Shadowrocket add a server of type HTTP or SOCKS5 with the QuanticData host, port, username (country, session ID, TTL) and password, enable it, and confirm the exit with a geolocation check; for Wi-Fi only, the built-in HTTP proxy setting under the network's details works without an app.
4. Run a small sample first and watch how iPhone and Shadowrocket responds; a residential IP is not a promise of access, acceptance or a particular success rate, and the apps' terms and the law apply to what you do through it.

Set it up for iPhone & Shadowrocket

QuanticData residential proxies are standard HTTP and SOCKS5 endpoints: a host, a port, a username and a password, shown in your dashboard the moment a plan is active. The username carries the country, the state and the city, and the session; host, port and password never change. Shadowrocket takes an HTTP or SOCKS5 server with authentication and routes every app on the phone through it, on Wi-Fi and on cellular. The built-in Wi-Fi proxy setting of iOS is the fallback when you cannot install an app.

host      PROXY_HOST                     # from your dashboard
port      PORT                           # the HTTP port, or the SOCKS5 port for a SOCKS5 node
username  USER-country-us-sid-iphone-ttl-120m
password  PASS

1. Get the four values. In your QuanticData dashboard pick the plan and use the endpoint generator: host, HTTP and SOCKS5 port, username with the country and a session ID with a lifetime (the whole phone will share it), and the password.
2. Add the server in Shadowrocket. Tap + on the home screen. Type: HTTP (for the HTTP port) or Socks5 (for the SOCKS5 port). Address: the host. Port: the port of that type. User: the username string, Password: the password. Leave TLS off. Save.
3. Select it and connect. Tap the new server so it becomes the active one, then switch Connected on; iOS asks once to add the VPN configuration. Global Routing: Proxy sends every app through the server; Config lets rules send some domains DIRECT.
4. One sticky session for the phone. The username carries USER-country-<cc>-sid-<id>-ttl-<minutes>: one session ID per phone, a lifetime that covers the day (up to 1440 minutes on mobile and Residential Premium, 120 on Residential Basic). A second identity is a second server entry with a different session ID; switch between them from the list.
5. DNS. Shadowrocket sends the hostname to the proxy, so the site is resolved at the exit; leave the DNS override at its default unless you have a reason. A domain listed as DIRECT in a Config rule bypasses the proxy for that domain.
6. Test the exit. Open https://ipinfo.io/json in Safari: the org should be a carrier (mobile) or a home ISP (residential), the country the one in the username. Then open the apps you care about; they see the same exit.
7. Wi-Fi only, without an app. Settings → Wi-Fi → the network's (i) → HTTP Proxy → Manual: server, port, Authentication on, username and password. It covers the apps that honour the system proxy on that network only; cellular and some apps stay outside, which is why Shadowrocket is the usual choice.
8. Typical errors. "Connection failed" or a timeout: the port belongs to the other protocol (HTTP port on a Socks5 entry, or the reverse), or the host is misspelled. HTTP 407 / authentication failed: a typo in the username, a password regenerated since, or a plan with no bandwidth left. Apps log you out at the same time every day: the ttl expired, raise it.