Data as of Nov 10, 2026

77.78.37.0/24

9 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
2
22% of its exits
Providers
35
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.4K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BartProxies
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.78.0.0/18
since Mar 2007
AS34569Residential658
74 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
77.78.0.0/1816,384BG-BTC-20070227Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAFeb 27, 2007abuse-ip@vivacom.bg
└ 77.78.37.0/24256Drujba-1-unl-pubHome subscribers with Public IP - Drujba1ASSIGNED PAJul 30, 2009abuse-ip@vivacom.bg
via BG-BTC-20070227

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

77.78.36.0/23

Routing history

Pattern
Stable
First seen
Oct 2024
Current origin since
Oct 2024 · 2.1 yr
Origin networks
1