Data as of Nov 21, 2026

89.189.156.0/22

16 residential-proxy exits · 30 days

JSC 'Ufanet'

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
16
1.6% of its addresses · 30 days
Always-on exits
1
6.3% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
20
selling exits here
Oct 22, 2026 – Nov 20, 2026

Exits seen per day

521 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.189.158.0/2418
89.189.156.0/2404
89.189.159.0/2404

Proxy providers listing exits

  • AnyIP
  • BirdProxies
  • BottingTools
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FloppyData
  • GEEKPROXY_TURBO
  • IPFly
  • IPMUSK
  • IPRoyal
  • NSocks
  • NovaProxy
  • Proxiware
  • Proxy4U
  • Proxying
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.189.128.0/19
since Apr 2007
AS24955Residential78
8 always on
JSC "Ufanet"
More specific

Announcements inside

PrefixOriginTypeHolderRPKI
89.189.157.0/24
since Apr 2024
AS24955ResidentialJSC "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.144.0/204,096UBNJSC "Ufanet"ASSIGNED PAMar 13, 2007abuse@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