Data as of Nov 10, 2026

83.239.166.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
23
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

1.1K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.239.128.0/18
since May 2005
AS33934Residential213
11 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 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
Jun 2019
Current origin since
Jun 2019 · 7.4 yr
Origin networks
1