Residential proxy · NRTH network
Residential IPs, per GB. No expiry games.
HTTP and SOCKS5 on the same port. Country, city and sticky session go inside the password; no library needed. The balance drops as you use it and its validity extends with every package.
- Countries
- 243
- Relayed · 24 h
- 516 MB
- Open connections
- 0
- Network
- Healthy
- Last check just now
The system’s own counters. This page refreshes every 10 seconds.
Credential grammar
The whole config is one line.
Targeting is appended to the password as “_key-value” tokens. No library, no plugin, no panel setting: curl is enough.
Other keys: region, city, isp, asn, zip, hardsession, lockedsession … Full list in the docs. Read the grammar →
How it works
- 01
Create an account, buy a package
An e-mail and a password. Pay by bank transfer or crypto; the balance is credited in GB.
- 02
Create a proxy user
A separate username and secret for every tool. Or whitelist an IP and connect without a password.
- 03
Connect
The gateway host and port are the same everywhere. Put the country or session in the password; the network resolves the rest.
Packages
Pay per GB. Every package extends the balance validity.
No packages are listed right now. Write to support for a manual credit.
Locations
243 countries
Pick the country with “_country-XX” in the password. Region and city lists are in the panel.
- TRTürkiye
- USUnited States
- GBUnited Kingdom
- DEGermany
- FRFrance
- NLNetherlands
- ESSpain
- ITItaly
- BRBrazil
- JPJapan
- CACanada
- AUAustralia
- +231more countries, all picked in the password · Read the grammar →
Questions
01Are the IPs really residential?
Yes. Traffic exits through the NRTH network on home-connection IPs. No data-centre IPs are handed out.
02What am I paying for, what is a GB?
Total data through the proxy (download + upload). 1 GB = 1024 MB. Every connection or request counts at least 512 bytes.
03When does the balance expire?
Every package extends the balance validity by its number of days, on top of the current expiry. After expiry connections are refused but the balance is not deleted: the next package makes it usable again.
04HTTP or SOCKS5?
Both, on the same port. The gateway reads the first byte and picks the protocol. HTTPS targets go through CONNECT.
05How do sticky sessions work?
Append “_session-<name>” to the password; as long as you use the same name you keep the same exit IP. “_lifetime-<min>” sets 1–1440 minutes. Session names are private to you: another customer using the same name gets a different IP.
06Can I pick a city, region or ISP?
Yes: country, region, city, continent, isp, asn and zip keys go in the password. Examples in the docs.
07Can I connect without a password?
Yes. Add an IP or CIDR to a proxy user in the panel; credential-less connections from that address are accepted as that user.
08Is there a concurrent-connection limit?
Depends on the package; unlimited packages exist. You can also cap each proxy user separately in the panel.
09Is there an API, are there rate limits?
Yes and no. Generate an API key in the panel and call with Bearer. Proxy generation, usage, orders, tickets: all REST. No request limits.
10How do I pay?
When you pick a package you get a reference code (NRTH-XXXXX). Put it in the transfer description or the crypto memo; once the payment is seen the balance is credited.
11What do you store?
Usage counters (bytes, requests, day) and account data. Target hosts are never stored; they live in memory only while a connection is open.
Gateway
Same host, same port. The rest goes in the password.
tunnel.nrth.solutions:1337 · HTTP and SOCKS5 · 0 open connections right now
Create account