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

95.43.208.0/24

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
AS8866
Type
Residential
58% of it

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
23
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

703 observations

Proxy providers listing exits

  • 711Proxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • Geonode
  • IPRoyal
  • Kookey
  • LemonBright
  • Oxylabs
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.43.208.0/20
since May 2016
AS8866Residential98
4 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.208.20/304Suvorovo_Net_PtPunknownASSIGNED PANov 13, 2020abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.24/304International_Aset_Bank_NesebarunknownASSIGNED PAMar 22, 2019abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.64/2816Ritum_FM_IsperiunknownASSIGNED PAMar 1, 2019abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.80/304Rahovec-Tourist-Gorna-OryahovitsaunknownASSIGNED PAMar 25, 2019abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.136/298Toplivo-CorporationToplivo-CorporationASSIGNED PADec 22, 2015abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.144/298Employment-Agency-PravetsunknownASSIGNED PAJan 24, 2022abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.152/298PolisanunknownASSIGNED PAOct 10, 2016abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.160/2732OMVOMVASSIGNED PAFeb 5, 2010abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.208/298Mena-Palace-Sunnu-BeachunknownASSIGNED PAApr 12, 2016abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.240/298Aset-Bank-Sofia-2unknownASSIGNED PAFeb 3, 2017abuse-ip@vivacom.bg
via BG-BTC-20081015
└ 95.43.208.248/298Coca-cola-HaskovounknownASSIGNED PAMar 15, 2017abuse-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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential14858%5
Business10842%11

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2011
Current origin since
Feb 2011 · 16 yr
Origin networks
1