Data as of Nov 19, 2026

89.21.133.0/24

13 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
13
5.1% of its addresses · 30 days
Always-on exits
1
7.7% of its exits
Providers
72
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

2.8K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLEETPROXY
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HASDATA
  • HELODATA
  • HideProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LemonLabs
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXIWARE_ECO
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • RolaProxy
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • VitalProxy
  • YumiProxy
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.21.132.0/22
since May 2007
AS15672Residential32
1 always on
OOO 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.133.0/24256TELECOM-TZ-NETNet for ip single static assignment clients MoscowASSIGNED PASep 2, 2022abuse@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
Nov 2014
Current origin since
Dec 2025 · 11 mo
Origin networks
1