Data as of Nov 12, 2026

83.228.28.0/22

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

Exits seen per day

1.0K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • FastProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPOasis
  • Infatica
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • NSocks
  • NiuProxy
  • NodeMaven
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • RoamProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.228.0.0/19
since Apr 2024
AS8866Residential60
2 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
83.228.0.0/1732,768BG-BTC-20020905Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAApr 26, 2004abuse-ip@vivacom.bg
└ 83.228.0.0/198,192BTC-BROADBAND-NETBTC Broadband ServiceASSIGNED PAFeb 11, 2005abuse-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