Data as of Nov 10, 2026

84.238.167.0/24

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Unknown
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
32
selling exits here
Oct 11, 2026 – Nov 9, 2026

Exits seen per day

362 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GonzoProxy
  • Infatica
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VitalData
  • VitalExclusive
  • 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.164.0 - 84.238.175.2553,072BG-BTC-20040810Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAJun 3, 2022abuse-ip@vivacom.bg
└ 84.238.167.0/24256Vivacom-DDoS-Voxility-LAN2unknownASSIGNED PAFeb 25, 2022abuse-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
Jun 2005
Current origin since
Nov 2017 · 9.0 yr
Origin networks
2
Last change of origin
Nov 2017
Recorded history

History

Handoffs
1