Data as of Nov 12, 2026

84.42.26.0/24

3 residential-proxy exits · 30 days

PJSC Rostelecom

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
28
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

212 observations

Proxy providers listing exits

  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • Kookey
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RapidProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VitalExclusive

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 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.24.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

Routing timeline

Covering aggregate above, the prefix's own history below

84.42.24.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