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

95.43.220.0/22

21 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
21
2.1% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
22
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

990 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
95.43.222.0/2407
95.43.223.0/2406
95.43.220.0/2404
95.43.221.0/2404

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • AnyIP
  • BestProxy
  • FastProxy
  • LUMIPROXY
  • LemonBright
  • NSocks
  • NiuProxy
  • Novada
  • PROXYSALE
  • PROXY_CC
  • Proxiware
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
95.43.208.0/20
since May 2016
AS8866Residential100
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.220.0/221,024BTC-Broadband-111BTC-Broadband NetworkASSIGNED PAOct 30, 2009abuse-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
Dec 2016 · 9.9 yr
Origin networks
2
Last change of origin
Dec 2016
Recorded history

History

Handoffs
1