Data as of Nov 18, 2026

81.4.242.0/23

3 residential-proxy exits · 30 days

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

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

Residential-proxy exits

Proxy exits
3
0.59% of its addresses · 30 days
Always-on exits
1
33% of its exits
Spread
1 of 2
/24s with at least one exit
Providers
28
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

1.7K observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • Evomi
  • Geonode
  • GonzoProxy
  • IPFly
  • Infatica
  • InfiniteProxies
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • VitalData
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.4.192.0/18
since May 2005
AS24626Residential3,899
21 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
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

Summary

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