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

95.43.116.0/22

18 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
18
1.8% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
23
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

499 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.43.116.0/2407
95.43.117.0/2404
95.43.119.0/2404
95.43.118.0/2403

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • Byteful
  • Decodo
  • EnigmaProxy
  • GSocks
  • Infatica
  • KocerRoxy
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.43.0.0/17
since May 2016
AS8866Residential731
56 always on
Vivacom Bulgaria EAD

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
95.42.0.0/15131,072BG-BTC-20081015Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAOct 15, 2008abuse-ip@vivacom.bg
└ 95.43.116.0/221,024BTC-BROADBAND-NET-12-1unknownASSIGNED PAApr 20, 2023abuse-ip@vivacom.bg
via BG-BTC-20081015

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
Nov 2009
Current origin since
Nov 2009 · 17 yr
Origin networks
1