Data as of Nov 16, 2026

136.169.254.0/24

4 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
4
1.6% of its addresses · 30 days
Providers
29
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

886 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GEEKPROXY_FLEX
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • ProxyWing
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
136.169.252.0/22
since Mar 2020
AS41704Residential19
3 always on
JSC "Ufanet"
136.169.240.0/20
since Nov 2011
AS41704Residential283
78 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
136.169.128.0/1732,768RU-ZAODS-20111121JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PANov 21, 2011abuse@ufanet.ru
└ 136.169.240.0/204,096UBNJSC "Ufanet"ASSIGNED PAAug 22, 2012abuse@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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Aug 2025
Current origin since
Aug 2025 · 1.3 yr
Origin networks
1