Data as of Nov 10, 2026

84.53.243.0/24

15 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Providers
48
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • 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.240.0/212,048MACROREGIONAL_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

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