Data as of Nov 17, 2026

81.18.153.0/24

42 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
Proxy exits nearby

Residential-proxy exits

Proxy exits
42
16% of its addresses · 30 days
Always-on exits
29
69% of its exits
Providers
50
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

53K observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GonzoProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • MangoProxy
  • Maskify
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PrivateProxy
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
81.18.128.0/19
since May 2005
AS24626Residential321
132 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.18.128.0/198,192RU-TRANSTELECOM-20020114Joint Stock Company TransTeleCom (ORG-CJSC19-RIPE) · RUALLOCATED PAMay 15, 2002abuse@ttk.ru
└ 81.18.153.0/24256TTK-MuromJSC "Company TransTeleCom"ASSIGNED PAJul 18, 2023abuse@ttk.ru
via RU-TRANSTELECOM-20020114

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
Reactivated
First seen
Oct 2007
Current origin since
Jul 2023 · 3.4 yr
Origin networks
2
Last change of origin
Jul 2023
Recorded history

History

Handoffs
1