Data as of Nov 14, 2026

77.79.186.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
36
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

4.4K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FLEETPROXY
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.79.184.0/22
since Apr 2020
AS24955Residential32
2 always on
JSC "Ufanet"
77.79.160.0/19
since Oct 2018
AS24955Residential3,836
781 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
77.79.128.0/1816,384RU-ZAODS-20070313JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PAMar 13, 2007abuse@ufanet.ru
└ 77.79.160.0/198,192UBNJSC "Ufanet"ASSIGNED PADec 17, 2007abuse@ufanet.ru
via RU-ZAODS-20070313

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
Apr 2024 · 2.6 yr
Origin networks
1