Where our IPs come from
Every proxy provider routes your traffic through someone else's IP address. The question that matters is whose, and how they got it. Our answer: we physically own and operate the modems our carrier IPs run on, and peer supply beyond that comes from partners who sign our agreement and pass checks we run on our own servers. Below is what we require, what we check, and what we do not yet verify.
Two supply sources. Owned hardware on real mobile carriers, plus peer supply from partners who must have the informed consent of device owners, sign an agreement in their legal name and declare where their supply comes from.
Source one: modems we physically own and operate
The first source is physical modems we own on real mobile carriers. We bought the hardware, we installed the SIM cards, we run the racks. When your request exits through one of these IPs, it exits through a device we control end to end - your traffic enters at gw.proxies.sx and leaves on a carrier connection we can point to on a shelf.
That means there is no mystery middle layer: no aggregator we license IPs from, no upstream reseller whose sourcing practices we have to take on faith. If you want to see how requests are routed across the fleet, thepool gatewaypage explains the mechanics.
Source two: peer supply - what we require, and what we check
Beyond our owned modems, partners can connect Android phones, Linux or Windows devices to the network. That supply is governed by a published contract (agents.proxies.sx/peer/skill.md).
What we require
- Informed consent of the owner of every device that shares bandwidth.
- A signed Partner Agreement 2.0 in the supplier's own legal name, as an individual or a company. We review and approve it before the relay admits the supplier's devices.
- An account-linked API key. Anonymous registration does not qualify a device for listed customer traffic.
- A supply-source declaration: device owners or upstream suppliers, apps and installation channels, country and network mix, and how permission is obtained and withdrawn.
What we check
- Server-side ASN classification of every IP as mobile carrier, residential or datacenter. The type a device reports about itself is ignored.
- An address on a hosting or datacenter network is never sold as residential or mobile. Such lines are a separate Datacenter (static) class, server-hosted and not residential, which is not on sale at the moment.
- An automatic test through the device's tunnel before it goes on sale, hourly re-verification of listed devices, and unlisting after an hour offline.
What we do not claim: submitted declarations are not independently verified KYC or proof of consent. Identity and business verification is being prepared separately. We do not publish the peer fleet's size or exit IPs. For a purchase review, use the sourcing evidence worksheet to record what the declaration covers and which controls you still need to see.
To see exactly what the software does on a supplier's device, read what runs on my device. To supply bandwidth yourself, start at /earn.
The contrast: pools of unknown provenance
Much of the residential proxy market works differently. Large pools aggregate IPs they do not control - bought from third-party suppliers, harvested through bundled SDKs, or resold through chains of brokers. Some of those IPs were obtained cleanly; some were abused or enrolled without meaningful consent. The operator often cannot tell you which is which, and neither can you. That is not a performance problem - it is a provenance problem, and it lands on the customer whose traffic was routed through it.
| Aggregated pool of unknown provenance | PROXIES.SX supply | |
|---|---|---|
| Who controls the exit device | Unknown - often a broker chain | Us (owned modems) or a supplier under a signed agreement |
| How the IP was obtained | Bought / bundled / resold - varies per IP | Hardware we purchased, or a declared supply source |
| IP type check | Often self-reported | Server-side ASN classification; hosted lines never sold as residential or mobile |
| Whose consent backs the supply | Often unverifiable | Ours (we own it), or device owners' informed consent required by contract |
| Independent KYC of suppliers | Varies | Being prepared; declarations are not yet independently verified |
How to check the route class for your own job
The public gateway feed counts eligible endpoints by country and pool. On November 20, 2026 at 16:34 UTC it listed ten carrier-modem endpoints in Georgia and zero peers there. In the United States, both pools had stock. Each reading describes the inventory at that time. It cannot establish who consented to a specific device joining.
When a customer needs a direct carrier route, choose mbl. For a residential peer, choose peer with iptype-residential. In the gateway reference you can see how to request each class. Record the requested class, date and actual country on a test endpoint you control. Ask us about the partner declaration and withdrawal process if your procurement review needs more than technical classification.
The Georgia guide shows why a shared modem count and an exclusive rental are separate. If you sell access to other companies, the wholesale sourcing guide explains what to pass on to your buyer. Check current rates by exit country when preparing a quote.
Frequently asked questions
We physically own and operate the modems our carrier IPs run on, all on real mobile carriers. A typical residential pool aggregates IPs it does not control, often bought from third-party suppliers or SDK bundles, so the operator cannot see how each IP was obtained.
Suppliers may share bandwidth only from devices whose owners have given informed consent. They sign Partner Agreement 2.0 in their own legal name, which we approve before the relay admits their devices, connect with their own account-linked API key, and declare where their supply comes from: device owners or upstream suppliers, apps and installation channels, country and network mix, and how permission is obtained and withdrawn.
IP type is classified on our servers by ASN; the type a device reports about itself is ignored. An address on a hosting or datacenter network is never sold as residential or mobile; such lines are a separate Datacenter (static) class, server-hosted and not residential, which is not on sale at the moment. A device goes on sale only after it passes an automatic test through its tunnel. Listed devices are re-verified hourly and unlisted after an hour offline.
Not yet. Submitted declarations are not independently verified KYC or proof of consent. Identity and business verification is being prepared separately. We would rather say that plainly than overstate it.
Go deeper
Ask us how our supply is sourced.
Owned modems on real carriers, plus peer supply under published requirements and server-side checks. If provenance matters to your compliance team, bring them to the call.