Data as of Nov 14, 2026

94.182.240.0/20

6 residential-proxy exits · 30 days

Aria Shatel PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
91% of it

Residential-proxy exits

Proxy exits
6
0.15% of its addresses · 30 days
Spread
1 of 16
/24s with at least one exit
Providers
26
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

410 observations

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EVOPROXY
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.182.192.0/18
since Jan 2026
AS31549Residential250
1 always on
Aria Shatel PJSC
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
94.182.254.0/24
since May 2024
AS205647ResidentialAria Shatel PJSC

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, 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.242.0/23512SHTL-NET-DED-9000110127unknownASSIGNED PAMar 4, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.16/2816SHTL-NET-DED-9000128899unknownASSIGNED PAJan 26, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.32/2816SHTL-NET-DED-9000109208unknownASSIGNED PASep 16, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.48/2816SHTL-NET-DED-9000127789unknownASSIGNED PAFeb 9, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.64/298SHTL-NET-DED-9000116560unknownASSIGNED PAJul 16, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.72/298SHTL-NET-DED-9000124724unknownASSIGNED PADec 8, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.80/2816SHTL-NET-DED-9000126507unknownASSIGNED PASep 7, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.96/2816SHTL-NET-DED-9000116929unknownASSIGNED PAJun 10, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.112/2816SHTL-NET-DED-9000125784unknownASSIGNED PAFeb 2, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.128/2664SHTL-NET-DED-9001300642unknownASSIGNED PAApr 20, 2022abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.253.192/2664SHTL-NET-DED-9002000377unknownASSIGNED PAFeb 12, 2022abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.254.0/24256SHTL-NET-DED-9000122117unknownASSIGNED PAOct 30, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.255.128/25128SHTL-NET-DED-9002000372unknownASSIGNED PAJun 29, 2022abuse@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

4,096 addresses
TypeAddressesShareRanges
Residential3,72891%3
Business3689.0%11

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

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