Data as of Nov 10, 2026

77.85.26.0/24

7 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
7
2.7% of its addresses · 30 days
Always-on exits
1
14% of its exits
Providers
33
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

6.9K observations

Proxy providers listing exits

  • 2Captcha
  • 911Proxy
  • BestProxy
  • BirdProxies
  • ByteProxies
  • Byteful
  • DataImpulse
  • EVOPROXY
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • GSocks
  • GoProxies
  • GonzoProxy
  • IPOasis
  • Infatica
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyHat
  • Proxying
  • Proxyma
  • RH7Proxy
  • Shifter
  • Smartproxy
  • Thordata
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
77.85.0.0/17
since Oct 2016
AS8866Residential1,125
38 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.85.0.0/1665,536BG-BTC-20070319Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAMar 19, 2007abuse-ip@vivacom.bg
└ 77.85.0.0/1816,384BTC-BROADBAND-NET-7BTC Broadband ServiceASSIGNED PAJun 26, 2007abuse-ip@vivacom.bg
via BG-BTC-20070319

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.85.24.0/21

Routing history

Pattern
Stable
First seen
May 2009
Current origin since
May 2009 · 18 yr
Origin networks
1