Data as of Nov 15, 2026

46.191.182.0/24

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

Exits seen per day

6.0K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • GSocks
  • Geonode
  • GonzoProxy
  • IPPeak
  • Infatica
  • InfiniteProxies
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.191.180.0/22
since Feb 2023
AS39593Residential520
113 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
46.191.128.0/1732,768RU-ZAODS-20101215JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PADec 15, 2010abuse@ufanet.ru
└ 46.191.160.0/198,192UBNJSC "Ufanet"ASSIGNED PANov 16, 2011abuse@ufanet.ru
via RU-ZAODS-20101215

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
Oct 2025 · 1.1 yr
Origin networks
1