Data as of Nov 18, 2026

95.105.115.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
Always-on exits
1
10% of its exits
Providers
41
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

3.3K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GloryCloud
  • GonzoProxy
  • HydraProxy
  • IPMUSK
  • IPRoyal
  • Infatica
  • KindProxy
  • LightningProxies
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RapidProxy
  • Shifter
  • SwiftProxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.105.112.0/22
since Mar 2020
AS41704Residential26
5 always on
JSC "Ufanet"
95.105.96.0/19
since Aug 2016
AS41704Residential866
224 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
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

Summary

Routing history

Pattern
Stable
First seen
Jun 2012
Current origin since
Aug 2025 · 1.3 yr
Origin networks
1