Data as of Nov 10, 2026

77.78.20.0/23

21 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
21
4.1% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
59
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

2.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.78.20.0/24014
77.78.21.0/2407

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • BestProxy
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • Kookey
  • LUMIPROXY
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • ProxyWing
  • PuraRoute
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TalorData
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

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 the announcement: those covering it, widest first, then every record inside it, 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.20.0/23512Razgrad-unlHome subscribers in city of RazgradASSIGNED 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

Summary

Routing history

Pattern
Rotating
First seen
Nov 2014
Current origin since
Sep 2024 · 2.1 yr
Origin networks
2
Last change of origin
Sep 2024
Recorded history

History

Handoffs
1