Data as of Nov 14, 2026

83.228.96.0/24

3 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Residential
88% of it

Residential-proxy exits

Proxy exits
3
1.2% of its addresses · 30 days
Providers
10
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

21 observations

Proxy providers listing exits

  • AnyIP
  • BirdProxies
  • FastProxy
  • FloppyData
  • GonzoProxy
  • IPFly
  • Infatica
  • LemonBright
  • PuraRoute
  • ThunderProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.228.96.0/21
since Dec 2025
AS8866Residential29
3 always on
Vivacom Bulgaria EAD

Registrations in this block

The registry's network records over this block, widest first, each 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.96.48/298Networking-Premium_SofiaunknownASSIGNED PAFeb 26, 2021abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 83.228.96.144/298School_St_Kiril_MedoiiunknownASSIGNED PADec 5, 2016abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 83.228.96.168/298Roca-KaspitchanunknownASSIGNED PAMar 19, 2021abuse-ip@vivacom.bg
via BG-BTC-20020905
└ 83.228.96.176/298ThermoiconomikunknownASSIGNED PAAug 21, 2017abuse-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.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

256 addresses
TypeAddressesShareRanges
Residential22488%4
Business3213%4

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

83.228.96.0/22

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1