Data as of Nov 11, 2026

83.228.4.0/22

1 residential-proxy exit · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
1
0.10% of its addresses · 30 days
Spread
1 of 4
/24s with at least one exit
Providers
4
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

39 observations

Proxy providers listing exits

  • BlurPath
  • CliProxy
  • IPPeak
  • NovProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
83.228.0.0/20
since May 2005
AS8866Residential5Vivacom Bulgaria EAD
83.228.0.0/19
since Apr 2024
AS8866Residential57
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
Jun 2015
Current origin since
Jun 2015 · 11 yr
Origin networks
1