Data as of Nov 14, 2026

87.254.170.0/23

2 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
2
0.39% of its addresses · 30 days
Spread
1 of 2
/24s with at least one exit
Providers
3
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • AnyIP
  • FastProxy
  • KocerRoxy

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
87.254.170.0/24
since Mar 2024
AS34754ResidentialVivacom Bulgaria EAD
87.254.171.0/24
since Mar 2024
AS8866Residential2Vivacom Bulgaria EAD

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
87.254.160.0/198,192BG-BTC-20081106Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 6, 2008abuse-ip@vivacom.bg
└ 87.254.170.0/24256TELNET-STUDENTSDHCP end usersASSIGNED PAApr 21, 2012abuse-ip@vivacom.bg
via BG-BTC-20081106
└ 87.254.171.0/24256TELNET-ARBANASSITelnet Ltd Arbanassi UsersASSIGNED PASep 27, 2009abuse-ip@vivacom.bg
via BG-BTC-20081106

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

Who has announced 87.254.160.0/19

87.254.160.0/19

Routing history

Pattern
Stable
First seen
Nov 2005
Current origin since
Nov 2008 · 18 yr
Origin networks
2
Last change of origin
Nov 2008
Recorded history

History

Handoffs
1