Data as of Nov 17, 2026

87.254.168.0/24

10 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
10
3.9% of its addresses · 30 days
Providers
42
selling exits here
Oct 18, 2026 – Nov 16, 2026

Exits seen per day

505 observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • EnigmaProxy
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FloppyData
  • GEEKPROXY_FLEX
  • GSocks
  • Geonix
  • GonzoProxy
  • HydraProxy
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Novada
  • PROXYSCRAPE
  • Proxies.fo
  • Proxy-Seller
  • Proxy302
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VibeProxies
  • VitalData
  • VitalExclusive

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.168.0/23512ZOOMBUL-NETZoomBul Ltd.ASSIGNED PANov 13, 2008abuse-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
Rotating
First seen
Nov 2023
Current origin since
Mar 2024 · 2.6 yr
Origin networks
2
Last change of origin
Mar 2024
Recorded history

History

Handoffs
1