Data as of Nov 16, 2026

87.126.236.0/24

22 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
22
8.6% of its addresses · 30 days
Providers
43
selling exits here
Oct 17, 2026 – Nov 15, 2026

Exits seen per day

363 observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • AnyIP
  • B2Proxy
  • BestProxy
  • BirdProxies
  • ByteProxies
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • GSocks
  • GloryCloud
  • IPFly
  • IPMUSK
  • IPPeak
  • Infatica
  • KindProxy
  • KocerRoxy
  • LemonBright
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Proxiware
  • Proxmint
  • Proxy4U
  • ProxyEmpire
  • ProxyWing
  • PuraRoute
  • RH7Proxy
  • RainProxy
  • RapidProxy
  • Shifter
  • SwiftProxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.126.192.0/18
since Oct 2006
AS8866Residential806
74 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.126.0.0/1665,536BG-BTC-20050905Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 5, 2005abuse-ip@vivacom.bg
└ 87.126.192.0/1816,384BTC-BROADBAND-NET-4BTC Broadband ServiceASSIGNED PAOct 4, 2006abuse-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

Summary

Routing history

Pattern
Stable
First seen
Jun 2008
Current origin since
Jun 2008 · 18 yr
Origin networks
1