Data as of Nov 14, 2026

178.134.240.0/24

3 residential-proxy exits · 30 days

JSC "Silknet"

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
Providers
26
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

284 observations

Proxy providers listing exits

  • 2Captcha
  • AnyIP
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FlashProxy
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • MangoProxy
  • NodeMaven
  • NovProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • Shifter
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
178.134.0.0/16
since Mar 2010
AS35805Residential3,257
356 always on
JSC "Silknet"

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
178.134.0.0/1665,536GE-UTG-20100323JSC "Silknet" (ORG-UTOG1-RIPE) · GEALLOCATED PAMar 23, 2010abuse@silknet.com
└ 178.134.201.0 - 178.134.255.25514,080SILKNET-BROADBANDJSC "Silknet" (ORG-UTOG1-RIPE) · GEASSIGNED PAJan 25, 2011abuse@silknet.com

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jul 2024
Current origin since
Jul 2024 · 2.3 yr
Origin networks
1