Data as of Nov 15, 2026

87.254.172.0/24

2 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
2
0.78% of its addresses · 30 days
Always-on exits
1
50% of its exits
Providers
28
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

3.7K observations

Proxy providers listing exits

  • 2Captcha
  • Ake.net
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • Decodo
  • FlashProxy
  • GoProxies
  • GonzoProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • Oxylabs
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • Shifter
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • Webshare

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.254.160.0/19
since Nov 2008
AS34754Residential113
11 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
87.254.160.0/198,192BG-BTC-20081106Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PANov 6, 2008abuse-ip@vivacom.bg
└ 87.254.172.0/23512VIVACOM-TELNET-SLAVQNI-2unknownASSIGNED PAFeb 16, 2024abuse-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

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Mar 2024
Current origin since
Mar 2024 · 2.6 yr
Origin networks
1