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

94.182.208.0/22

6 residential-proxy exits · 30 days

Aria Shatel PJSC

Announcement
94.182.208.0/20
RPKI valid
Announced by
AS31549
Type
Residential
52% of it

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
44
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

405 observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.182.208.0/2403
94.182.211.0/2402
94.182.209.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Evomi
  • FlashProxy
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NodeMaven
  • NodeProxy
  • Novada
  • Proxio
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.182.192.0/19
since Apr 2020
AS31549Residential69
1 always on
Aria Shatel PJSC
94.182.192.0/18
since Jan 2026
AS31549Residential253
1 always on
Aria Shatel PJSC
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
94.182.208.0/24
since Oct 2024
AS31549Residential3Aria 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.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
└ 94.182.209.16/2816SHTL-NET-DED-9000106808unknownASSIGNED PAJun 24, 2018abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.40/298SHTL-NET-DED-9000115933unknownASSIGNED PANov 9, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.48/2816SHTL-NET-DED-9000104601unknownASSIGNED PAOct 30, 2017abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.64/2816SHTL-NET-DED-9000112107unknownASSIGNED PADec 9, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.80/2816SHTL-NET-DED-9000120929unknownASSIGNED PANov 26, 2024abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.96/2816SHTL-NET-DED-9000126506unknownASSIGNED PASep 21, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.112/2816SHTL-NET-DED-9000104862unknownASSIGNED PANov 6, 2016abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.128/2816SHTL-NET-DED-9000102039unknownASSIGNED PAOct 18, 2017abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.144/2816SHTL-NET-DED-9000103253unknownASSIGNED PAOct 18, 2017abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.160/2816SHTL-NET-DED-9000120132unknownASSIGNED PAMay 7, 2023abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.176/2816SHTL-NET-DED-9000125488unknownASSIGNED PADec 8, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.192/298SHTL-NET-DED-9000115332unknownASSIGNED PAOct 23, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.200/298SHTL-NET-DED-9000122550unknownASSIGNED PAMar 9, 2024abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.208/2816SHTL-NET-DED-9000125488unknownASSIGNED PADec 8, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.209.224/2816SHTL-NET-DED-9000107067unknownASSIGNED PAApr 4, 2018abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.210.0/24256SHTL-NET-DED-9000110344unknownASSIGNED PADec 22, 2019abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.211.32/298SHTL-NET-DED-9007500019unknownASSIGNED PAJan 20, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.211.48/298SHTL-NET-DED-9007500024unknownASSIGNED PAMay 20, 2020abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.211.96/2816SHTL-NET-DED-9007500062unknownASSIGNED PAJul 25, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.211.112/2816SHTL-NET-DED-9007500065unknownASSIGNED PAAug 15, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.211.136/298SHTL-NET-DED-9007500121unknownASSIGNED PAFeb 24, 2024abuse@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

1,024 addresses
TypeAddressesShareRanges
Residential53652%10
Business48848%35

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
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