LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

136.169.162.0/23

4 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
136.169.160.0/22
RPKI valid
Announced by
AS24955
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
0.78% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
25
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
136.169.163.0/2403
136.169.162.0/2401

Proxy providers listing exits

  • Ake.net
  • BartProxies
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GSocks
  • IPFly
  • IPPeak
  • Infatica
  • LemonPrime
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
136.169.160.0/19
since Feb 2023
AS24955Residential800
172 always on
JSC "Ufanet"
136.169.128.0/18
since Nov 2011
AS24955Residential3,733
503 always on
JSC "Ufanet"

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
136.169.128.0/1732,768RU-ZAODS-20111121JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PANov 21, 2011abuse@ufanet.ru
└ 136.169.128.0/1816,384UBNJSC "Ufanet"ASSIGNED PANov 23, 2011abuse@ufanet.ru
via RU-ZAODS-20111121

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

136.169.160.0/22

Routing history

Pattern
Stable
First seen
Apr 2020
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1