Data as of Nov 12, 2026

88.87.6.0/24

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Business

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
7
selling exits here
Oct 13, 2026 – Nov 11, 2026

Exits seen per day

81 observations

Proxy providers listing exits

  • 911Proxy
  • Ake.net
  • AnyIP
  • RainProxy
  • Shifter
  • Thordata
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
88.87.0.0/19
since Jan 2007
AS34754Residential147
13 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
88.87.0.0/198,192BG-BTC-20060221Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAFeb 21, 2006abuse-ip@vivacom.bg
└ 88.87.6.0/25128TELNET-NAT-POOLSTelnet NAT poolsASSIGNED PADec 2, 2009abuse-ip@vivacom.bg
via BG-BTC-20060221
└ 88.87.6.128/25128TELNET-DRYANOVOTelnet users in DryanovoASSIGNED PADec 13, 2009abuse-ip@vivacom.bg
via BG-BTC-20060221

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
Rotating
First seen
Jun 2010
Current origin since
Mar 2024 · 2.7 yr
Origin networks
2
Last change of origin
Mar 2024
Recorded history

History

Handoffs
1