Data as of Nov 18, 2026

79.140.16.0/23

4 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
33
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

8.4K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • Geonode
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxying
  • Proxyma
  • Shifter
  • Smartproxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.140.16.0/20
since Oct 2007
AS41704Residential348
47 always on
JSC "Ufanet"
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
79.140.17.0/24
since Dec 2025
AS41704Residential4
1 always on
JSC "Ufanet"

Registrations in this block

The registry's network records over this block, widest first, each 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

79.140.16.0/22

Routing history

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