Data as of Nov 13, 2026

46.10.128.0/22

46 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
46
4.5% of its addresses · 30 days
Always-on exits
1
2.2% of its exits
Spread
4 of 4
/24s with at least one exit
Providers
53
selling exits here
Oct 14, 2026 – Nov 12, 2026

Exits seen per day

1.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.10.131.0/2418
46.10.128.0/24014
46.10.129.0/24014
46.10.130.0/24010

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • B2Proxy
  • BestProxy
  • BirdProxies
  • BlurPath
  • ByteProxies
  • Byteful
  • CliProxy
  • EZProxies
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • GSocks
  • GloryCloud
  • GonzoProxy
  • IPFly
  • IPOasis
  • IPPeak
  • Infatica
  • InfiniteProxies
  • KindProxy
  • LemonBright
  • LemonPrime
  • LightningProxies
  • LudaxProxy
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NodeProxy
  • NovProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYSCRAPE
  • Proxiware
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • StrikeProxy
  • Thordata
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.10.128.0/20
since Dec 2025
AS8866Residential64
1 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
46.10.0.0/1665,536BG-BTC-20100913Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PASep 13, 2010abuse-ip@vivacom.bg
└ 46.10.128.0/221,024BTC-BROADBAND-NET-31BTC Broadband ServiceASSIGNED PAJul 2, 2015abuse-ip@vivacom.bg
via BG-BTC-20100913

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
Nov 2012
Current origin since
Nov 2012 · 14 yr
Origin networks
1