Data as of Nov 10, 2026

77.78.22.0/23

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

Exits seen per day

1.6K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
77.78.22.0/24113
77.78.23.0/24017

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • Ake.net
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • Proxying
  • Proxyma
  • RainProxy
  • Shifter
  • StrikeProxy
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

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.22.0/24256Center-2-unl-pubHome subscribers with Public IP - Center2ASSIGNED PAJul 30, 2009abuse-ip@vivacom.bg
via BG-BTC-20070227
└ 77.78.23.0/24256Center-1-unl-pubHome subscribers with Public IP - Center1ASSIGNED 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
Stable
First seen
Oct 2024
Current origin since
Oct 2024 · 2.1 yr
Origin networks
1