Data as of Nov 18, 2026

87.126.229.0/24

16 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

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

Residential-proxy exits

Proxy exits
16
6.3% of its addresses · 30 days
Providers
43
selling exits here
Oct 19, 2026 – Nov 17, 2026

Exits seen per day

887 observations

Proxy providers listing exits

  • BirdProxies
  • ByteProxies
  • Byteful
  • DataImpulse
  • EnigmaProxy
  • FLAMEPROXIES_BASIC
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • GloryCloud
  • GonzoProxy
  • IPROCKET_BASIC
  • Infatica
  • KindProxy
  • KocerRoxy
  • LemonBright
  • LemonLabs
  • LemonPrime
  • MangoProxy
  • MoMoProxy
  • NextProxy
  • NodeProxy
  • NovaProxy
  • PROXIES.RIP
  • PROXYSCRAPE
  • PacketStream
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • Proxyma
  • RainProxy
  • RapidProxy
  • SPYDERPROXY_PREMIUM
  • Shifter
  • ThunderProxy
  • VantageProxies
  • VitalExclusive

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
87.126.192.0/18
since Oct 2006
AS8866Residential818
93 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.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

87.126.228.0/23

Routing history

Pattern
Stable
First seen
Oct 2007
Current origin since
Oct 2007 · 19 yr
Origin networks
1