Data as of Nov 12, 2026

89.189.136.0/22

7 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
7
0.68% of its addresses · 30 days
Always-on exits
1
14% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
25
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

1.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.189.136.0/2411
89.189.138.0/2404
89.189.137.0/2402

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LightningProxies
  • NextProxy
  • NodeMaven
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.189.128.0/19
since Apr 2007
AS24955Residential80
2 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
89.189.128.0/198,192RU-ZAODS-20060524JSC "Ufanet" (ORG-ZS2-RIPE) · RUALLOCATED PAMay 24, 2006abuse@ufanet.ru
└ 89.189.128.0/204,096UBNJSC "Ufanet"ASSIGNED PASep 15, 2006abuse@ufanet.ru
via RU-ZAODS-20060524

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 2020
Current origin since
Apr 2020 · 6.6 yr
Origin networks
1