Data as of Nov 18, 2026

136.169.226.0/23

1 residential-proxy exit · 30 days

JSC 'Ufanet'

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

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

Exits seen per day

125 observations

Proxy providers listing exits

  • Ake.net
  • BlurPath
  • BottingTools
  • Byteful
  • CliProxy
  • DataImpulse
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPRoyal
  • KindProxy
  • Kookey
  • NextProxy
  • NiuProxy
  • Novada
  • Proxy4U
  • PuraRoute
  • RH7Proxy
  • RapidProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
136.169.224.0/20
since Mar 2012
AS24955Residential1,785
542 always on
JSC "Ufanet"
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
136.169.226.0/24
since Apr 2024
AS24955ResidentialJSC "Ufanet"
136.169.227.0/24
since Apr 2024
AS24955Residential1
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
136.169.128.0/1732,768RU-ZAODS-20111121JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PANov 21, 2011abuse@ufanet.ru
└ 136.169.224.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

136.169.224.0/21

Routing history

Pattern
Stable
First seen
Jun 2013
Current origin since
Feb 2023 · 3.8 yr
Origin networks
1