LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

83.239.48.0/20

38 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
38
0.93% of its addresses · 30 days
Always-on exits
4
11% of its exits
Spread
13 of 16
/24s with at least one exit
Providers
61
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

7.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.239.49.0/2414
83.239.54.0/2414
83.239.48.0/2413
83.239.53.0/2412
83.239.56.0/2406
83.239.57.0/2404
83.239.51.0/2403
83.239.50.0/2403
83.239.62.0/2403
83.239.52.0/2402
83.239.60.0/2402
83.239.55.0/2401
83.239.63.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.239.32.0/19
since Mar 2006
AS25490Residential71
6 always on
PJSC Rostelecom
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 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.32.0/198,192Macroregional_SouthOJSC Rostelecom Macroregional Branch SouthASSIGNED PAFeb 4, 2005abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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