Data as of Nov 12, 2026

89.16.103.0/24

11 residential-proxy exits · 30 days

Joint Stock Company TransTeleCom

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

Residential-proxy exits

Proxy exits
11
4.3% of its addresses · 30 days
Always-on exits
3
27% of its exits
Providers
53
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

4.1K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • B2Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GonzoProxy
  • HydraProxy
  • IPFly
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYWING_BASIC
  • Proxio
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalData
  • VitalExclusive
  • VitalProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
89.16.96.0/19
since Jul 2006
AS20870Residential149
17 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.16.96.0/198,192RU-TRANSTELECOM-20060706Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PAApr 8, 2015abuse@ttk.ru
└ 89.16.103.0 - 89.16.104.255512IPGALNETInternet providerASSIGNED PAApr 8, 2015abuse@ttk.ru
via RU-TRANSTELECOM-20060706

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

Summary

Routing history

Pattern
Stable
First seen
May 2012
Current origin since
Nov 2017 · 9.0 yr
Origin networks
2
Last change of origin
Nov 2017
Recorded history

History

Handoffs
1