Data as of Nov 14, 2026

94.41.88.0/24

2 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
2
0.78% of its addresses · 30 days
Providers
25
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

195 observations

Proxy providers listing exits

  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • IPRoyal
  • Infatica
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxying
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.41.88.0/22
since Apr 2020
AS24955Residential3JSC "Ufanet"
94.41.64.0/19
since Oct 2018
AS24955Residential137
19 always on
JSC "Ufanet"
94.41.0.0/17
since Nov 2008
AS24955Residential670
107 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.0.0/1732,768UBNJSC "Ufanet"ASSIGNED PAMay 21, 2008abuse@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.3 yr
Origin networks
1