Data as of Nov 12, 2026

83.228.32.0/22

3 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
3
0.29% of its addresses · 30 days
Spread
3 of 4
/24s with at least one exit
Providers
28
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

2.3K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.228.33.0/2401
83.228.34.0/2401
83.228.35.0/2401

Proxy providers listing exits

  • BirdProxies
  • BottingTools
  • Byteful
  • CliProxy
  • Decodo
  • EnigmaProxy
  • GSocks
  • IPPeak
  • Infatica
  • KocerRoxy
  • LemonBright
  • MangoProxy
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • ProxyHat
  • Proxyma
  • RainProxy
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.228.32.0/20
since Apr 2024
AS8866Residential17Vivacom 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
83.228.0.0/1732,768BG-BTC-20020905Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAApr 26, 2004abuse-ip@vivacom.bg
└ 83.228.32.0/212,048ADSL-POOL-RUSE-VTBTC Broadband ServiceASSIGNED PAJun 11, 2008abuse-ip@vivacom.bg
via BG-BTC-20020905

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
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1