Data as of Nov 11, 2026

89.237.49.0/24

63 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

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

Residential-proxy exits

Proxy exits
63
25% of its addresses · 30 days
Providers
45
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.6K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Datarama
  • Decodo
  • EnigmaProxy
  • Evomi
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYSCRAPE
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • Proxyma
  • PuraRoute
  • Q2IP
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Registrations in this block

The registry's network records over this block, widest first, each 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.48.0/221,024MSS-SUTTK-CHELSouthern Urals TransTelecom MSS-DHCPASSIGNED PASep 20, 2024abuse@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 89.237.48.0/22

89.237.48.0/22

Routing history

Pattern
Stable
First seen
Jun 2008
Current origin since
Jun 2008 · 18 yr
Origin networks
1