Data as of Nov 15, 2026

79.140.22.0/24

9 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
9
3.5% of its addresses · 30 days
Providers
30
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

213 observations

Proxy providers listing exits

  • Ake.net
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPROCKET_BASIC
  • Infatica
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_BASIC
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.140.20.0/22
since Mar 2020
AS41704Residential28JSC "Ufanet"
79.140.16.0/20
since Oct 2007
AS41704Residential346
43 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
79.140.16.0/204,096RU-ZAODS-20071004JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PAOct 4, 2007abuse@ufanet.ru
└ 79.140.16.0/212,048UBNJSC "Ufanet"ASSIGNED PAOct 4, 2007abuse@ufanet.ru
via RU-ZAODS-20071004

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