LAYER3 INTEL
Get started
Sign in
Data as of Nov 14, 2026

83.228.36.0/22

6 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
6
0.59% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
16
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

279 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
83.228.39.0/2403
83.228.36.0/2401
83.228.37.0/2401
83.228.38.0/2401

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • BestProxy
  • FastProxy
  • LemonBright
  • NSocks
  • PROXYSALE
  • PROXY_CC
  • Proxiware
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive
  • ZENPROXY_PREMIUM

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Nov 2005
Current origin since
Nov 2005 · 21 yr
Origin networks
1