Data as of Nov 15, 2026

94.182.216.0/23

3 residential-proxy exits · 30 days

Aria Shatel PJSC

Announcement
RPKI valid
Announced by
Type
Residential
72% of it

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

609 observations
  • Residential
  • Business

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • FlashProxy
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyStyler
  • Proxyma
  • SOTAPROXY
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.182.192.0/19
since Apr 2020
AS31549Residential68
1 always on
Aria Shatel PJSC
94.182.192.0/18
since Jan 2026
AS31549Residential260
1 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
94.182.0.0 - 94.183.148.255103,680IR-RASANA-20080917Aria Shatel PJSC (ORG-ART1-RIPE) · IRALLOCATED PAJul 4, 2025abuse@rasana.net
└ 94.182.216.32/298SHTL-NET-DED-9000123702unknownASSIGNED PAJun 22, 2024abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.40/298SHTL-NET-DED-9000111739unknownASSIGNED PADec 20, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.48/298SHTL-NET-DED-9000111739unknownASSIGNED PANov 17, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.56/298SHTL-NET-DED-9000124129unknownASSIGNED PAJul 26, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.80/298SHTL-NET-DED-9000119125unknownASSIGNED PADec 20, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.96/298SHTL-NET-DED-9000127547unknownASSIGNED PASep 17, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.104/298SHTL-NET-DED-9000115297unknownASSIGNED PAOct 30, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.112/298SHTL-NET-DED-9000122896unknownASSIGNED PAAug 8, 2018abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.120/298SHTL-NET-DED-9000125332unknownASSIGNED PAFeb 3, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.128/298SHTL-NET-DED-9000113926unknownASSIGNED PAAug 14, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.144/2816SHTL-NET-DED-9000112297unknownASSIGNED PAMay 9, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.168/298SHTL-NET-DED-9041800055unknownASSIGNED PAJun 8, 2022abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.208/298SHTL-NET-DED-9000121404unknownASSIGNED PASep 2, 2018abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.216/298SHTL-NET-DED-9000103659unknownASSIGNED PAJan 23, 2019abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.224/298SHTL-NET-DED-9000119334unknownASSIGNED PAJul 8, 2024abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.232/298SHTL-NET-DED-9000108095unknownASSIGNED PAApr 10, 2019abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.216.240/298SHTL-NET-DED-9000111831unknownASSIGNED PANov 14, 2020abuse@rasana.net
via IR-RASANA-20080917

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

512 addresses
TypeAddressesShareRanges
Residential36872%7
Business14428%17

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

94.182.208.0/20

Routing history

Pattern
Stable
First seen
Aug 2010
Current origin since
Aug 2016 · 10 yr
Origin networks
1