Data as of Nov 13, 2026

94.182.18.0/23

11 residential-proxy exits · 30 days

Aria Shatel PJSC

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
58% of it
Recent change
New origin Aug 2026
from AS31549 Aria Shatel PJSC, after 7.6 years unannounced

Residential-proxy exits

Proxy exits
11
2.1% of its addresses · 30 days
Always-on exits
3
27% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
34
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.0K observations
  • Residential
  • Business

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.182.18.0/24310
94.182.19.0/2401

Proxy providers listing exits

  • 2Captcha
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • FlashProxy
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.182.16.0/20
since Aug 2016
AS31549Residential54
4 always on
Aria Shatel PJSC
94.182.0.0/18
since Jan 2026
AS31549Residential307
6 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.18.16/298SHTL-NET-DED-9001301502unknownASSIGNED PAFeb 7, 2024abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.18.72/298SHTL-NET-DED-9001300708unknownASSIGNED PAJun 8, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.18.112/298SHTL-NET-DED-9001300208unknownASSIGNED PAJun 29, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.0/2664SHTL-NET-DED-9001301868unknownASSIGNED PAJul 6, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.64/2732SHTL-NET-DED-9001301172unknownASSIGNED PANov 2, 2022abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.96/2816SHTL-NET-DED-9001301454unknownASSIGNED PAJun 29, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.128/2816SHTL-NET-DED-9001300744unknownASSIGNED PAMar 9, 2021abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.152/298SHTL-NET-DED-9001301866unknownASSIGNED PAMay 5, 2025abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.160/2732SHTL-NET-DED-9001300743unknownASSIGNED PAOct 16, 2018abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.224/298NET-SHTL-DED-9001301119unknownASSIGNED PAJan 17, 2023abuse@rasana.net
via IR-RASANA-20080917
└ 94.182.19.240/2816SHTL-NET-DED-9001300415unknownASSIGNED PAJul 15, 2025abuse@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
Residential29658%8
Business21642%11

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Dec 2018
Current origin since
Aug 2026 · 3 mo
Origin networks
1