Data as of Nov 13, 2026

89.21.131.40/29

1 residential-proxy exit · 30 days

OOO Telecom TZ

Announcement
No RPKI
Announced by
Type
Business
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
1
13% of its addresses · 30 days
Providers
40
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

100 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • IPOasis
  • Infatica
  • LemonLabs
  • LightningProxies
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.21.128.0/22
since Sep 2006
AS15672Residential24OOO Telecom TZ

Registrations in this block

The registry's network records over this block, widest first, each 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.131.40/298IBTECH-NETOOO AbyteckASSIGNED PAJun 29, 2023abuse@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

89.21.131.0/24

Routing history

Pattern
Stable
First seen
Jan 2015
Current origin since
Dec 2025 · 11 mo
Origin networks
1