Data as of Nov 13, 2026

81.4.243.0/24

3 residential-proxy exits · 30 days

Limited Liability Company 'TTK-Svyaz' · space held by Joint Stock Company TransTeleCom

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Always-on exits
1
33% of its exits
Providers
32
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

401 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • EnigmaProxy
  • Evomi
  • FastProxy
  • GSocks
  • GhostConnect
  • GonzoProxy
  • HideProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • LudaxProxy
  • MangoProxy
  • NovaProxy
  • PrivateProxy
  • ProxiesVision
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.4.192.0/18
since May 2005
AS24626Residential3,866
21 always on
Joint Stock Company TransTeleCom

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
81.4.192.0/1816,384RU-TRANSTELECOM-20020515Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PAMay 15, 2002abuse@ttk.ru
└ 81.4.242.0/23512TMK-VladimirVladimir, RussiaASSIGNED PANov 1, 2013abuse@ttk.ru
via RU-TRANSTELECOM-20020515

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

81.4.242.0/23

Routing history

Pattern
Stable
First seen
Oct 2012
Current origin since
May 2021 · 5.5 yr
Origin networks
2
Last change of origin
May 2021
Recorded history

History

Handoffs
1