Data as of Nov 15, 2026

87.126.18.0/24

4 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
4
1.6% of its addresses · 30 days
Providers
35
selling exits here
Oct 16, 2026 – Nov 14, 2026

Exits seen per day

860 observations

Proxy providers listing exits

  • 2Captcha
  • 9HTTP
  • AETHYN_BASIC
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • FlashProxy
  • FloppyData
  • GSocks
  • GonzoProxy
  • IPMUSK
  • IPOasis
  • Infatica
  • KocerRoxy
  • LemonBright
  • LightningProxies
  • MangoProxy
  • NSocks
  • NovaProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • Shifter
  • Smartproxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.126.0.0/17
since Dec 2005
AS8866Residential2,092
49 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.126.0.0/1665,536BG-BTC-20050905Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 5, 2005abuse-ip@vivacom.bg
└ 87.126.4.0 - 87.126.64.25515,616BTC-Broadband-2unknownASSIGNED PAMay 19, 2016abuse-ip@vivacom.bg
via BG-BTC-20050905

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

87.126.16.0/21

Routing history

Pattern
Stable
First seen
Apr 2010
Current origin since
Apr 2010 · 17 yr
Origin networks
1