Data as of Nov 13, 2026

185.44.8.0/24

6 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
6
2.3% of its addresses · 30 days
Always-on exits
2
33% of its exits
Providers
34
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlexyProxies
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
185.44.8.0/22
since Nov 2014
AS60095Residential274
81 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
185.44.8.0/221,024RU-ZAODS-20131227JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PADec 27, 2013abuse@ufanet.ru
└ 185.44.8.0/23512UBNJSC "Ufanet"ASSIGNED PADec 30, 2013abuse@ufanet.ru
via RU-ZAODS-20131227

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
Nov 2014
Current origin since
Jun 2025 · 1.4 yr
Origin networks
1