Data as of Nov 11, 2026

46.241.44.0/24

8 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
8
3.1% of its addresses · 30 days
Always-on exits
2
25% of its exits
Providers
28
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

1.4K observations

Proxy providers listing exits

  • 2Captcha
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • GSocks
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Proxio
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.241.0.0/17
since Feb 2011
AS21127Residential940
285 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
46.241.0.0/1732,768RU-TTKS-20101223Limited Liability Company "TTK-Svyaz" (ORG-LLC51-RIPE) · RUALLOCATED PADec 23, 2010nmc@ttk.ru
└ 46.241.0.0/1816,384ZSTTK-RTL-NETJSC "Zap-Sib TransTeleCom"ASSIGNED PADec 27, 2010nmc@ttk.ru
via RU-TTKS-20101223

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
Dec 2020
Current origin since
Dec 2020 · 5.9 yr
Origin networks
1