Data as of Nov 14, 2026

79.100.160.0/22

4 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
4
0.39% of its addresses · 30 days
Always-on exits
1
25% of its exits
Spread
3 of 4
/24s with at least one exit
Providers
26
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

11K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
79.100.161.0/2412
79.100.160.0/2401
79.100.162.0/2401

Proxy providers listing exits

  • 711Proxy
  • BottingTools
  • Byteful
  • CoreProxy
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • KocerRoxy
  • LemonBright
  • Novada
  • Oxylabs
  • PacketStream
  • Proxiware
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Thordata
  • ThunderProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
79.100.0.0/16
since Nov 2007
AS8866Residential9,129
110 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
May 2008
Current origin since
May 2008 · 19 yr
Origin networks
1