Data as of Nov 10, 2026

83.239.2.0/24

4 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
33
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

694 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.239.0.0/18
since Mar 2011
AS25490Residential163
16 always on
PJSC Rostelecom
83.239.0.0/16
since Sep 2018
AS12389Residential1,087
59 always on
PJSC Rostelecom

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
83.239.0.0/1665,536RU-RTK-20040225PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 25, 2004abuse@rt.ru
└ 83.239.0.0/204,096Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAMay 21, 2004abuse@rt.ru
via RU-RTK-20040225

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

83.239.0.0/20

Routing history

Pattern
Stable
First seen
Mar 2006
Current origin since
Mar 2006 · 21 yr
Origin networks
1