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

94.41.56.0/22

2 residential-proxy exits · 30 days

JSC 'Ufanet'

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

Residential-proxy exits

Proxy exits
2
0.20% of its addresses · 30 days
Spread
2 of 4
/24s with at least one exit
Providers
11
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

20 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
94.41.56.0/2401
94.41.59.0/2401

Proxy providers listing exits

  • Byteful
  • GSocks
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
94.41.0.0/18
since Oct 2018
AS24955Residential168
17 always on
JSC "Ufanet"
94.41.0.0/17
since Nov 2008
AS24955Residential677
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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Oct 2009
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1