Data as of Nov 10, 2026

82.231.185.0/24

6 residential-proxy exits · 30 days

Free SAS

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
6
2.3% of its addresses · 30 days
Always-on exits
1
17% of its exits
Providers
39
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

5.4K observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • Shifter
  • StrikeProxy
  • Thordata
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
82.224.0.0/11
since May 2005
AS12322Residential31,140
4,780 always on
Free SAS

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
82.224.0.0/112,097,152FR-PROXAD-20031104Free SAS (ORG-PISP1-RIPE) · FRALLOCATED PANov 4, 2003abuse@proxad.net
└ 82.231.184.0/23512FR-PROXAD-ADSLProxad / Free SASASSIGNED PASep 6, 2005abuse@proxad.net
via FR-PROXAD-20031104

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

82.231.160.0/19

Routing history

Pattern
Stable
First seen
Feb 2026
Current origin since
Feb 2026 · 9 mo
Origin networks
1