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

84.42.20.0/24

15 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
15
5.9% of its addresses · 30 days
Always-on exits
1
6.7% of its exits
Providers
61
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

2.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • KindProxy
  • LemonLabs
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • RolaProxy
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • TORCHPROXIES_X
  • TrueProxies
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.42.0.0/19
since Mar 2024
AS21378Residential312
24 always on
PJSC Rostelecom
84.42.0.0/17
since Jun 2020
AS12389Residential3,299
564 always on
PJSC Rostelecom

Registrations in this block

The registry's network records over this block, widest first, each 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.16.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

84.42.16.0/21

Routing history

Pattern
Stable
First seen
Jun 2005
Current origin since
Mar 2024 · 2.7 yr
Origin networks
2
Last change of origin
Nov 2008
Recorded history

History

Handoffs
1