LAYER3 INTEL
Get started
Sign in
Data as of Nov 12, 2026

89.237.32.0/21

42 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

Announcement
this exact prefix
No RPKI
Announced by
AS20485
Type
Residential

Residential-proxy exits

Proxy exits
42
2.1% of its addresses · 30 days
Always-on exits
15
36% of its exits
Spread
4 of 8
/24s with at least one exit
Providers
77
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

19K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.237.37.0/241438
89.237.33.0/2412
89.237.32.0/2401
89.237.34.0/2401

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • HydraProxy
  • IPFly
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MarsProxies
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RoamProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • StrikeProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
89.237.37.0/24
since Jan 2019
AS20485Residential38
14 always on
Joint Stock Company TransTeleCom

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.32.0/23512ACCKOM-SUTTK-ORSKunknownASSIGNED PANov 20, 2006abuse@ttk.ru
via RU-TRANSTELECOM-20060620
└ 89.237.34.0/24256ACCKOM-SUTTK-ORSKunknownASSIGNED PAOct 12, 2007abuse@ttk.ru
via RU-TRANSTELECOM-20060620
└ 89.237.35.0 - 89.237.36.255512ACCKOM-SUTTK-ORSKunknownASSIGNED PANov 29, 2007abuse@ttk.ru
via RU-TRANSTELECOM-20060620
└ 89.237.37.0/24256NOKS-NET-SUTTK-ORS"NoKS"ASSIGNED PAJan 15, 2009abuse@ttk.ru
via RU-TRANSTELECOM-20060620
└ 89.237.38.0/24256ORSKTELEKOM-SUTTK-ORSOrskTelekom Ltd.ASSIGNED PAMar 17, 2009abuse@ttk.ru
via RU-TRANSTELECOM-20060620
└ 89.237.39.0/24256SUTTKSouthern Urals TransTelecomASSIGNED PADec 5, 2007abuse@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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Nov 2006
Current origin since
Sep 2018 · 8.1 yr
Origin networks
2
Last change of origin
Sep 2018
Recorded history

History

Handoffs
1