Data as of Nov 19, 2026

89.21.157.0/24

9 residential-proxy exits · 30 days

OOO Telecom TZ

Announcement
this exact prefix
No RPKI
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Providers
42
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

466 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • INSTANTSOCKS_PREMIUM
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LemonLabs
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_PREMIUM
  • VantageProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.21.152.0/21
since Aug 2007
AS15672Residential11OOO Telecom TZ

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.21.128.0/198,192RU-TZ-20060920OOO Telecom TZ (ORG-TT4-RIPE) · RUALLOCATED PASep 20, 2006abuse@tz.ru
└ 89.21.157.0/24256TELECOM-TZ-NETNet for ip single static assignment clients MskASSIGNED PAFeb 10, 2014abuse@tz.ru
via RU-TZ-20060920

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
Dec 2025
Current origin since
Dec 2025 · 11 mo
Origin networks
1