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

84.42.0.0/21

40 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
40
2.0% of its addresses · 30 days
Always-on exits
14
35% of its exits
Spread
5 of 8
/24s with at least one exit
Providers
76
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

26K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
84.42.4.0/241320
84.42.5.0/2413
84.42.2.0/24010
84.42.6.0/2404
84.42.7.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • GeekProxy
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • Maskify
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PSBProxy
  • PacketStream
  • PrivateByte
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.42.0.0/19
since Mar 2024
AS21378Residential303
22 always on
PJSC Rostelecom
84.42.0.0/17
since Jun 2020
AS12389Residential3,281
550 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
84.42.0.0/1732,768RU-RTK-20040910PJSC Rostelecom (ORG-JR8-RIPE) · RUALLOCATED PAAug 30, 2019abuse@rt.ru
└ 84.42.0.0/198,192MACROREGIONAL_CENTERunknownSUB-ALLOCATED PAJan 12, 2017abuse@rt.ru
via RU-RTK-20040910
└ 84.42.0.0/212,048MACROREGIONAL_CENTEROJSC Rostelecom, Tver branchASSIGNED PAJan 12, 2017abuse@rt.ru
via MACROREGIONAL_CENTER

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 2005
Current origin since
Mar 2024 · 2.7 yr
Origin networks
2
Last change of origin
Jun 2009
Recorded history

History

Handoffs
1