Data as of Nov 16, 2026

94.182.208.0/24

3 residential-proxy exits · 30 days

Aria Shatel PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business
84% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
26
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

99 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.182.208.0/20
since Aug 2016
AS31549Residential18
1 always on
Aria Shatel PJSC
94.182.192.0/19
since Apr 2020
AS31549Residential68
1 always on
Aria Shatel PJSC
94.182.192.0/18
since Jan 2026
AS31549Residential263
1 always on
Aria 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.208.0/2816SHTL-NET-DED-9000112372unknownASSIGNED PADec 9, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.16/2816SHTL-NET-DED-9000121701unknownASSIGNED PASep 22, 2024abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.48/298SHTL-NET-DED-9000122930unknownASSIGNED PANov 26, 2022abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.64/2816SHTL-NET-DED-90010226unknownASSIGNED PAOct 28, 2017abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.80/2816SHTL-NET-DED-9000116013unknownASSIGNED PANov 3, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.96/2816SHTL-NET-DED-9000115157unknownASSIGNED PAAug 2, 2022abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.112/2816SHTL-NET-DED-9000110969unknownASSIGNED PAMar 1, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.128/2816SHTL-NET-DED-9000109539unknownASSIGNED PAOct 29, 2017abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.144/2816SHTL-NET-DED-9000125488unknownASSIGNED PAMar 2, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.160/2816SHTL-NET-DED-9000115576unknownASSIGNED PANov 15, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.176/298SHTL-NET-DED-9000127198unknownASSIGNED PASep 3, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.184/298SHTL-NET-DED-9000123502unknownASSIGNED PAJan 18, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.192/2816SHTL-NET-DED-9000107316unknownASSIGNED PASep 7, 2026abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.224/2816SHTL-NET-DED-9000123892unknownASSIGNED PAOct 19, 2024abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.208.240/2816SHTL-NET-DED-9000125488unknownASSIGNED PADec 2, 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

256 addresses
TypeAddressesShareRanges
Business21684%15
Residential4016%3

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
May 2020
Current origin since
Oct 2024 · 2.1 yr
Origin networks
1