Data as of Nov 12, 2026

83.239.142.0/23

4 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
27
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

200 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.239.143.0/2402
83.239.142.0/2401

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PacketStream
  • PrivateByte
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • Proxyma
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.239.128.0/18
since May 2005
AS33934Residential209
11 always on
PJSC Rostelecom
83.239.0.0/16
since Sep 2018
AS12389Residential1,083
57 always on
PJSC Rostelecom

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
83.239.0.0/1665,536RU-RTK-20040225PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAFeb 25, 2004abuse@rt.ru
└ 83.239.128.0/1816,384Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAFeb 27, 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

Summary

Routing history

Pattern
Stable
First seen
Aug 2019
Current origin since
Aug 2019 · 7.2 yr
Origin networks
1