Data as of Nov 18, 2026

188.168.71.0/24

3 residential-proxy exits · 30 days

Limited Liability Company 'TTK-Svyaz'

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

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
30
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

46 observations

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FloppyData
  • GSocks
  • Geonix
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonLabs
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxy-Seller
  • ProxyEmpire
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.168.0.0/16
since Sep 2009
AS15774Residential9,456
298 always on
Limited Liability Company "TTK-Svyaz"

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
188.168.0.0/1665,536RU-TTKS-20090616Limited Liability Company "TTK-Svyaz" (ORG-LLC51-RIPE) · RUALLOCATED PAJun 24, 2021nmc@ttk.ru
└ 188.168.71.0/24256Chita_TTK-RTL-POOL7TTK-Chita/BRAS in ShimanovskASSIGNED PAFeb 4, 2010nmc@ttk.ru
via RU-TTKS-20090616

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
Jun 2012
Current origin since
Feb 2017 · 9.8 yr
Origin networks
2
Last change of origin
Feb 2017
Recorded history

History

Handoffs
2