Data as of Nov 12, 2026

84.241.30.0/24

8 residential-proxy exits · 30 days

Aria Shatel PJSC

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Providers
41
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

3.0K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • CoreProxy
  • DataImpulse
  • FlashProxy
  • GSocks
  • GeekProxy
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • MagneticProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PSBProxy
  • PrivateByte
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyStyler
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • SpyderProxy
  • TrustProxy
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
84.241.0.0/18
since Aug 2016
AS31549Residential225
7 always on
Aria Shatel PJSC

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
84.241.0.0/1816,384IR-RASANA-20040610Aria Shatel PJSC (ORG-ART1-RIPE) · IRALLOCATED PAJun 10, 2004abuse@rasana.net
└ 84.241.0.0/198,192SHTL-DSL-THRSHATEL DSL NetworkASSIGNED PANov 5, 2010abuse@rasana.net
via IR-RASANA-20040610

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.241.16.0/20

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
Aug 2010 · 16 yr
Origin networks
2
Last change of origin
Aug 2010
Recorded history

History

Handoffs
1