Data as of Nov 13, 2026

84.238.136.0/22

26 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
26
2.5% of its addresses · 30 days
Always-on exits
1
3.8% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
47
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

2.6K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 911Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPOasis
  • IPPeak
  • Infatica
  • KindProxy
  • LUMIPROXY
  • LemonBright
  • LemonPrime
  • LudaxProxy
  • MangoProxy
  • NSocks
  • NodeMaven
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • PuraRoute
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

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
84.238.134.0 - 84.238.159.2556,656BG-BTC-20040810Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAOct 2, 2020abuse-ip@vivacom.bg
└ 84.238.136.0/212,048BTC-BROADBAND-NET-123BTC Broadband ServiceASSIGNED PAJul 13, 2015abuse-ip@vivacom.bg
via BG-BTC-20040810

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

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jan 2014
Current origin since
Jan 2014 · 13 yr
Origin networks
1