Data as of Nov 11, 2026

95.43.26.0/23

17 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
17
3.3% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
31
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

284 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.43.27.0/2409
95.43.26.0/2408

Proxy providers listing exits

  • 911Proxy
  • ASHBURNPROXIES
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlexyProxies
  • GSocks
  • Infatica
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • PROXYSCRAPE
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.43.0.0/17
since May 2016
AS8866Residential707
47 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.0.0 - 95.43.113.25529,184BTC-BROADBAND-NET-12unknownASSIGNED 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

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2013
Current origin since
Jan 2013 · 14 yr
Origin networks
1