Data as of Nov 15, 2026

94.41.173.0/24

10 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
10
3.9% of its addresses · 30 days
Providers
30
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.41.172.0/22
since Mar 2020
AS41704Residential29
2 always on
JSC "Ufanet"
94.41.160.0/19
since Feb 2009
AS41704Residential3,248
791 always on
JSC "Ufanet"

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.41.0.0/1665,536RU-ZAODS-20080521JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PAMay 21, 2008abuse@ufanet.ru
└ 94.41.160.0/198,192UBNJSC "Ufanet"ASSIGNED PAFeb 6, 2009abuse@ufanet.ru
via RU-ZAODS-20080521

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2025
Current origin since
Aug 2025 · 1.2 yr
Origin networks
1