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

87.254.162.0/24

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
87.254.162.0/23
RPKI valid
Announced by
AS8866
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Always-on exits
1
25% of its exits
Providers
30
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

889 observations

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • ASHBURNPROXIES
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • GonzoProxy
  • IPOasis
  • Infatica
  • LightningProxies
  • MangoProxy
  • NSocks
  • NovaProxy
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • VibeProxies
  • VitalData
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.254.160.0/19
since Nov 2008
AS34754Residential110
10 always on
Vivacom 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.160.0/221,024VIVACOM-TELNET-VT-GOunknownASSIGNED PAFeb 15, 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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

87.254.162.0/23

Routing history

Pattern
Rotating
First seen
May 2009
Current origin since
Mar 2024 · 2.6 yr
Origin networks
2
Last change of origin
Mar 2024
Recorded history

History

Handoffs
1