Data as of Nov 12, 2026

84.53.241.0/24

17 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
17
6.6% of its addresses · 30 days
Always-on exits
1
5.9% of its exits
Providers
43
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VibeProxies
  • 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