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

94.182.232.0/21

173 residential-proxy exits · 30 days

Aria Shatel PJSC

Announcement
94.182.224.0/20
RPKI valid
Announced by
AS31549
Type
Residential
88% of it

Residential-proxy exits

Proxy exits
173
8.4% of its addresses · 30 days
Spread
2 of 8
/24s with at least one exit
Providers
22
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

779 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.182.237.0/24092
94.182.236.0/24081

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • GSocks
  • Geonix
  • GonzoProxy
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • RainProxy
  • Shifter
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.182.192.0/18
since Jan 2026
AS31549Residential252
2 always on
Aria Shatel PJSC
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
94.182.239.0/24
since Jul 2022
AS31549ResidentialAria 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.236.0/23512SHTL-NET-DED-9000106483unknownASSIGNED PAFeb 25, 2019abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.8/298SHTL-NET-DED-9000129840unknownASSIGNED PAJul 1, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.16/2816SHTL-NET-DED-9000117838unknownASSIGNED PASep 10, 2022abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.32/298SHTL-NET-DED-9000119551unknownASSIGNED PADec 23, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.48/2816SHTL-NET-DED-9000125095unknownASSIGNED PAMar 11, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.64/2816SHTL-NET-DED-9000126842unknownASSIGNED PAAug 10, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.80/2816SHTL-NET-DED-9000129688unknownASSIGNED PAJul 29, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.96/298SHTL-NET-DED-9000120599unknownASSIGNED PASep 12, 2023abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.104/298SHTL-NET-DED-9000126899unknownASSIGNED PASep 7, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.112/2816SHTL-NET-DED-9000123666unknownASSIGNED PAApr 14, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.239.128/25128SHTL-NET-DED-9008300058unknownASSIGNED PANov 5, 2019abuse@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

2,048 addresses
TypeAddressesShareRanges
Residential1,80888%3
Business24012%10

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

94.182.224.0/20

Routing history

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