Data as of Nov 14, 2026

185.79.32.0/22

37 residential-proxy exits · 30 days

PLJ TELECOM sp. z o.o.

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

Residential-proxy exits

Proxy exits
37
3.6% of its addresses · 30 days
Always-on exits
1
2.7% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
48
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

8.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
185.79.35.0/2419
185.79.32.0/24016
185.79.33.0/2407
185.79.34.0/2405

Proxy providers listing exits

  • 2Captcha
  • 2Extract
  • 711Proxy
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • Infatica
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • TORCHPROXIES_X
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
185.79.32.0/221,024PL-PLJPL-20141128PLJ TELECOM sp. z o.o. (ORG-PTC10-RIPE) · PLALLOCATED PANov 28, 2014abuse@plj.pl
└ 185.79.32.0/24256Client-IPunknownASSIGNED PAAug 3, 2018abuse@plj.pl
via PL-PLJPL-20141128
└ 185.79.33.0 - 185.79.34.255512Client-IPunknownASSIGNED PAAug 3, 2018abuse@plj.pl
via PL-PLJPL-20141128
└ 185.79.35.0/24256Client-IPunknownASSIGNED PAAug 3, 2018abuse@plj.pl
via PL-PLJPL-20141128

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Dec 2014
Current origin since
Dec 2014 · 12 yr
Origin networks
1