Data as of Nov 20, 2026

87.126.228.0/23

29 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
29
5.7% of its addresses · 30 days
Spread
2 of 2
/24s with at least one exit
Providers
58
selling exits here
Oct 21, 2026 – Nov 19, 2026

Exits seen per day

1.8K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
87.126.229.0/24017
87.126.228.0/24012

Proxy providers listing exits

  • AETHYN_ELITE
  • Ake.net
  • BirdProxies
  • BlurPath
  • ByteProxies
  • Byteful
  • CYBERYOZH
  • DataImpulse
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • HASDATA
  • HELODATA
  • IPFly
  • Infatica
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXIES.RIP
  • PROXYLANE
  • PROXYSCRAPE
  • PacketStream
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyGeo
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • RolaProxy
  • SOTAPROXY
  • Shifter
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.126.192.0/18
since Oct 2006
AS8866Residential833
88 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
Oct 2007
Current origin since
Oct 2007 · 19 yr
Origin networks
1