Data as of Nov 18, 2026

95.160.17.0/24

4 residential-proxy exits · 30 days

Vectra S.A.

Announcement
RPKI valid
Announced by
Type
Internet provider
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
35
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

772 observations

Proxy providers listing exits

  • 2Extract
  • 711Proxy
  • 9Proxy
  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • EnigmaProxy
  • FastProxy
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonode
  • GonzoProxy
  • Infatica
  • InfiniteProxies
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • PrivateProxy
  • Proxy-Cheap
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • SOTAPROXY
  • Shifter
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.160.0.0/17
since Oct 2013
AS29314Residential461
39 always on
Vectra S.A.

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
95.160.0.0/1665,536PL-DAMINET-20081222Vectra S.A. (ORG-TKDS1-RIPE) · PLALLOCATED PADec 22, 2008abuse@vectra.pl
└ 95.160.16.0/221,024VECTRANETVectra S.A. -= BUSINESS P2P CONNECTIONS =ASSIGNED PADec 27, 2011abuse@vectra.pl
via PL-DAMINET-20081222

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

95.160.16.0/22

Routing history

Pattern
Stable
First seen
Feb 2010
Current origin since
Aug 2016 · 10 yr
Origin networks
1