What the label actually says
| Label | What it describes | What it does not describe |
|---|---|---|
| Residential | The address block is registered to a consumer or household ISP | Who uses it, how many, how it performs, or what its reputation is today |
| Hosting / data centre | The block is registered to a hosting provider | Whether the service accepts or rejects it — that is the platform's decision |
| Mobile | The block belongs to a mobile carrier | Stability, throughput, or sharing with other subscribers |
Address classification feeds into risk scoring. It is one input among several, which is exactly why a residential label can fail and a hosting label can succeed for the same service on different days.
What usually changes, and what does not
| Problem | Does exit type help | Why |
|---|---|---|
| Region notice on a public page | Possibly | The region decision may weigh address class |
| Account-level restriction after login | No | The decision follows the account, not the address |
| Payment or billing inconsistency | No | Billing details are stored on the account |
| Blocked by site policy regardless of address class | No | Policy is not a classification question |
| Slow streaming at peak | Usually worse | Shared residential routes are rarely optimised for sustained throughput |
Shared addresses cut both ways
Residential addresses are finite and often shared. That has two consequences. Your session may inherit a reputation built by other users of the same address, including behaviour you would not choose. And your own activity may be attributed to that shared address by whoever else is watching. Neither is visible from the provider's page.
Verify instead of trusting the label
- Connect through the exit and read the address from a reporting service.
- Compare against two independent data sources; they disagree on hosting ranges more often than people expect.
- Check what the actual target service does — the service's decision is the outcome you care about, not the database's opinion.
- Record the classification each source gave, the time, and the service's response. If sources disagree, write that down rather than picking the convenient one.
Before paying more
Establish that the failure is classification. The test is simple: same account, same hour, same action, one exit of each type. If both fail identically, the gate is elsewhere — account, payment, plan or policy — and a more expensive address will not move it. If both succeed, you have learned that the service is not the constraint.
Performance expectations
Residential routes are designed for households, not for sustained cross-border throughput. Expect higher latency variance and lower peak-hour headroom than a well-connected hosting node. If your task is streaming or large transfers, test at your actual hour before committing to a plan built around residential exits.
What to record
- Exit IP as observed, and the two sources used to classify it.
- The target service's response, in its own words.
- Whether the same account behaves differently on another exit type.
- Latency and one sustained transfer result at peak hour.
- The provider's stated terms for how the address is sourced — recorded as a claim, not as verification.
Scope
This page describes what the label does and does not establish. It names no provider, publishes no test results for specific services, and makes no claim that any address class passes any platform's checks.