Data as of Nov 11, 2026

87.126.4.0/22

27 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
27
2.6% of its addresses · 30 days
Spread
4 of 4
/24s with at least one exit
Providers
33
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

578 observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.126.6.0/2409
87.126.5.0/2408
87.126.4.0/2405
87.126.7.0/2405

Proxy providers listing exits

  • 711Proxy
  • Ake.net
  • AnyIP
  • BestProxy
  • ByteProxies
  • Byteful
  • CatProxies
  • EZProxies
  • FlexyProxies
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPPeak
  • Infatica
  • KindProxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Proxy-Seller
  • Proxy4U
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • Shifter
  • Smartproxy
  • Thordata
  • VitalExclusive

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

Who has announced 87.126.0.0/17

87.126.0.0/17

Routing history

Pattern
Stable
First seen
Dec 2005
Current origin since
Dec 2005 · 21 yr
Origin networks
1