Data as of Nov 12, 2026

83.228.72.0/24

9 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
9
3.5% of its addresses · 30 days
Always-on exits
2
22% of its exits
Providers
36
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

17K observations

Proxy providers listing exits

  • 711Proxy
  • 9Proxy
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • Decodo
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GSocks
  • Geonode
  • GoProxies
  • GonzoProxy
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • Kookey
  • LemonBright
  • MangoProxy
  • NovaProxy
  • Oxylabs
  • PrivateProxy
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • RapidProxy
  • Smartproxy
  • StrikeProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.228.64.0/20
since Oct 2022
AS8866Residential50
2 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.72.0/23512TELESAT-BGTELESAT-StrazhitsaASSIGNED PAJul 18, 2012abuse-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

83.228.72.0/23

Routing history

Pattern
Stable
First seen
Jul 2012
Current origin since
Jul 2012 · 14 yr
Origin networks
1