Data as of Nov 22, 2026

95.105.104.0/23

3 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
26
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

1.6K observations

Proxy providers listing exits

  • 2Captcha
  • AETHYN_ELITE
  • BirdProxies
  • ByteProxies
  • Byteful
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • GonzoProxy
  • HASDATA
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.105.96.0/19
since Aug 2016
AS41704Residential869
209 always on
JSC "Ufanet"
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
95.105.104.0/24
since Apr 2024
AS41704Residential3JSC "Ufanet"

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.105.0.0/1732,768RU-ZAODS-20091210JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PADec 10, 2009abuse@ufanet.ru
└ 95.105.96.0/198,192UBNJSC "Ufanet"ASSIGNED PANov 18, 2011abuse@ufanet.ru
via RU-ZAODS-20091210

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

95.105.104.0/22

Routing history

Pattern
Stable
First seen
Mar 2020
Current origin since
Mar 2020 · 6.7 yr
Origin networks
1