Data as of Nov 14, 2026

188.44.99.0/24

5 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
5
2.0% of its addresses · 30 days
Providers
36
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

193 observations

Proxy providers listing exits

  • 2Captcha
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • GSocks
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPRoyal
  • Infatica
  • KindProxy
  • LightningProxies
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalData
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
188.44.96.0/19
since Nov 2011
AS21127Residential170
31 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.44.96.0/198,192RU-TTKS-20111004Limited Liability Company "TTK-Svyaz" (ORG-LLC51-RIPE) · RUALLOCATED PAOct 4, 2011nmc@ttk.ru
└ 188.44.96.0/221,024ZSTTK-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PANov 21, 2011nmc@ttk.ru
via RU-TTKS-20111004

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
Jan 2012
Current origin since
Jul 2019 · 7.4 yr
Origin networks
2
Last change of origin
Jul 2019
Recorded history

History

Handoffs
1