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

79.100.178.0/24

5 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
79.100.176.0/21
RPKI valid
Announced by
AS8866
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
5
2.0% of its addresses · 30 days
Providers
36
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

97 observations

Proxy providers listing exits

  • BirdProxies
  • BlurPath
  • ByteProxies
  • Byteful
  • DataImpulse
  • FastProxy
  • FlexyProxies
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPRoyal
  • Infatica
  • KindProxy
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • VantageProxies

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.100.0.0/16
since Nov 2007
AS8866Residential9,139
102 always on
Vivacom Bulgaria EAD

Registrations in this block

The registry's network records over this block, widest first, each 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.167.0 - 79.100.191.2556,400BTC-BROADBAND-NET-12unknownASSIGNED 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

79.100.176.0/21

Routing history

Pattern
Stable
First seen
Mar 2008
Current origin since
Mar 2008 · 19 yr
Origin networks
1