Data as of Nov 13, 2026

79.100.92.0/24

8 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
8
3.1% of its addresses · 30 days
Always-on exits
1
13% of its exits
Providers
35
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.2K observations

Proxy providers listing exits

  • Ake.net
  • BlurPath
  • Byteful
  • DataImpulse
  • FastProxy
  • GSocks
  • GloryCloud
  • IPRoyal
  • Infatica
  • KindProxy
  • KocerRoxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxiware
  • Proxmint
  • Proxy4U
  • ProxyRack
  • ProxyWing
  • Proxyma
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • Thordata
  • VitalExclusive
  • ZENPROXY_PREMIUM

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.0.0/1732,768BTC-BROADBAND-NET-9BTC Broadband ServiceASSIGNED PAJun 20, 2008abuse-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

79.100.80.0/20

Routing history

Pattern
Stable
First seen
Dec 2007
Current origin since
Dec 2007 · 19 yr
Origin networks
1