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

84.53.239.0/24

21 residential-proxy exits · 30 days

PJSC Rostelecom

Announcement
84.53.192.0/18
RPKI valid
Announced by
AS34168
Type
Residential
Risk
0 / 100 · Low
Proxy exits nearby

Residential-proxy exits

Proxy exits
21
8.2% of its addresses · 30 days
Always-on exits
5
24% of its exits
Providers
50
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

6.6K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GoProxies
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Registrations in this block

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

RangeAddressesNetnameHolderTypeCreatedAbuse contact
84.53.192.0/1816,384RU-RTK-20041105PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PANov 5, 2004abuse@rt.ru
└ 84.53.236.0/221,024MACROREGIONAL_CENTEROJSC Rostelecom, Vladimir branchASSIGNED PANov 24, 2025abuse@rt.ru
via RU-RTK-20041105

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

Who has announced 84.53.192.0/18

84.53.192.0/18

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1