Data as of Nov 14, 2026

188.168.78.0/24

30 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
30
12% of its addresses · 30 days
Always-on exits
1
3.3% of its exits
Providers
68
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

4.5K observations

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • AnyIP
  • B2Proxy
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • BuyingProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • HideProxy
  • IPFly
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonLabs
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYON
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • ProxyEmpire
  • ProxyGeo
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • ResiProxies
  • SPYDERPROXY_PREMIUM
  • Shifter
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_LITE

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.168.0.0/16
since Sep 2009
AS15774Residential9,323
278 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.72.0/212,048TTK-RTL-POOL1TTK-Ural/BRAS1 in Ekaterinburg (static pool)ASSIGNED PADec 27, 2012nmc@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
Sep 2012
Current origin since
Sep 2012 · 14 yr
Origin networks
1