Data as of Nov 15, 2026

89.237.21.0/24

18 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

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

Residential-proxy exits

Proxy exits
18
7.0% of its addresses · 30 days
Always-on exits
2
11% of its exits
Providers
39
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

11K observations

Proxy providers listing exits

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

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.237.0.0/1816,384RU-TRANSTELECOM-20060620Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PAJun 20, 2006abuse@ttk.ru
└ 89.237.21.0/24256MSS-SUTTK-CLKSouthern Urals TransTelecom MSS DHCP + IPoEASSIGNED PAAug 28, 2009abuse@ttk.ru
via RU-TRANSTELECOM-20060620

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2009
Current origin since
Apr 2022 · 4.6 yr
Origin networks
1