LAYER3 INTEL
Get started
Sign in
Data as of Nov 15, 2026

109.171.76.0/24

1 residential-proxy exit · 30 days

Limited Liability Company 'TTK-Svyaz'

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

Residential-proxy exits

Proxy exits
1
0.39% of its addresses · 30 days
Always-on exits
1
100% of its exits
Providers
20
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

572 observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • GonzoProxy
  • IPPeak
  • Infatica
  • LightningProxies
  • MangoProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • Shifter
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
109.171.0.0/17
since Dec 2009
AS21127Residential872
152 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
109.171.0.0/1732,768RU-TTKS-20091117Limited Liability Company "TTK-Svyaz" (ORG-LLC51-RIPE) · RUALLOCATED PANov 17, 2009nmc@ttk.ru
└ 109.171.64.0/1816,384ZSTTK-RTL-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PAMar 29, 2010nmc@ttk.ru
via RU-TTKS-20091117

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2012
Current origin since
Sep 2019 · 7.1 yr
Origin networks
2
Last change of origin
Sep 2019
Recorded history

History

Handoffs
1