Data as of Nov 15, 2026

79.100.165.0/24

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
6.6% of its addresses · 30 days
Providers
32
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

539 observations

Proxy providers listing exits

  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • GSocks
  • IPPeak
  • IPROCKET_BASIC
  • IPROCKET_PREMIUM
  • Infatica
  • KocerRoxy
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.100.0.0/16
since Nov 2007
AS8866Residential9,206
114 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
79.100.0.0/1665,536BG-BTC-20071109Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 9, 2007abuse-ip@vivacom.bg
└ 79.100.128.0 - 79.100.165.2559,728BTC-BROADBAND-NET-10unknownASSIGNED PANov 9, 2026abuse-ip@vivacom.bg
via BG-BTC-20071109

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
Jun 2008
Current origin since
Jun 2008 · 18 yr
Origin networks
1