Data as of Nov 13, 2026

95.43.28.0/23

8 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
8
1.6% of its addresses · 30 days
Always-on exits
1
13% of its exits
Spread
2 of 2
/24s with at least one exit
Providers
57
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

6.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.43.28.0/2416
95.43.29.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPOasis
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • MarsProxies
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.43.0.0/17
since May 2016
AS8866Residential711
48 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
Oct 2014
Current origin since
Oct 2014 · 12 yr
Origin networks
1