Data as of Nov 22, 2026

188.168.32.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
Always-on exits
2
67% of its exits
Providers
30
selling exits here
Oct 23, 2026 – Nov 21, 2026

Exits seen per day

7.8K observations

Proxy providers listing exits

  • 711Proxy
  • B2Proxy
  • BirdProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • HASDATA
  • IPPeak
  • Infatica
  • LOKIPROXY
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • PROXYLANE
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • SOTAPROXY
  • Shifter
  • VantageProxies
  • VitalExclusive
  • YumiProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.168.0.0/16
since Sep 2009
AS15774Residential9,482
306 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.32.0/24256TTK-RTL-POOL1TTK-Baikal/BRAS2 in Ulan-Ude (static pool)ASSIGNED PASep 11, 2009nmc@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
May 2011
Current origin since
Feb 2018 · 8.8 yr
Origin networks
2
Last change of origin
Feb 2018
Recorded history

History

Handoffs
1