Data as of Nov 14, 2026

89.237.14.0/23

132 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
132
26% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
68
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

3.7K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
89.237.15.0/24085
89.237.14.0/24046

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • ASHBURNPROXIES
  • Ake.net
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • Datarama
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FLEETPROXY
  • FastProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GhostConnect
  • GonzoProxy
  • HELODATA
  • HPROXY
  • HideProxy
  • IPFly
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • InfiniteProxies
  • LOKIPROXY
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • NextProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYFALL
  • PROXYLANE
  • PROXYON
  • PROXYSAVER
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • ResiProxies
  • SPYDERPROXY_BASIC
  • SPYDERPROXY_PREMIUM
  • Shifter
  • VantageProxies
  • VitalExclusive
  • YumiProxy
  • ZENPROXY_PREMIUM

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.14.0/23512RRS74-SUTTK-TRKRadioreleynaya svyaz Ltd, ISPASSIGNED PANov 24, 2010abuse@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
Dec 2010
Current origin since
Apr 2018 · 8.6 yr
Origin networks
2
Last change of origin
Apr 2018
Recorded history

History

Handoffs
1