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

87.254.176.0/22

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
87.254.160.0/19
RPKI valid
Announced by
AS34754
Type
Residential

Residential-proxy exits

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

Exits seen per day

213 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.254.178.0/2402
87.254.176.0/2401
87.254.177.0/2401

Proxy providers listing exits

  • AnyIP
  • BottingTools
  • FastProxy
  • FloppyData
  • LemonBright
  • Oxylabs
  • Proxiware
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
87.254.176.0/24
since Mar 2024
AS8866Residential1Vivacom Bulgaria EAD
87.254.177.0/24
since Mar 2024
AS8866Residential1Vivacom Bulgaria EAD
87.254.178.0/23
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.176.0/23512TELNET-KARTALATelnet Ltd Kartala UsersASSIGNED PADec 7, 2016abuse-ip@vivacom.bg
via BG-BTC-20081106
└ 87.254.178.0/23512TELNET-PISHMANA2Telnet Ltd Home UsersASSIGNED PADec 13, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
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