LAYER3 INTEL
Get started
Sign in
Data as of Nov 10, 2026

77.78.14.0/24

18 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
18
7.0% of its addresses · 30 days
Providers
44
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

889 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • GonzoProxy
  • IPOasis
  • Infatica
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LightningProxies
  • MangoProxy
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • 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 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.14.0/24256ruse14PPPoE RS 14ASSIGNED PAJul 11, 2017abuse-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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

77.78.14.0/23

Routing history

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