Data as of Nov 14, 2026

46.10.42.0/24

27 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
27
11% of its addresses · 30 days
Always-on exits
1
3.7% of its exits
Providers
69
selling exits here
Oct 15, 2026 – Nov 13, 2026

Exits seen per day

2.5K observations

Proxy providers listing exits

  • 711Proxy
  • 911Proxy
  • Ake.net
  • AnyIP
  • BartProxies
  • BirdProxies
  • BlurPath
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • DataImpulse
  • EVOPROXY
  • EZProxies
  • EnigmaProxy
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • GSocks
  • Geonode
  • GloryCloud
  • GoProxies
  • GonzoProxy
  • HELODATA
  • HideProxy
  • IPFly
  • IPMUSK
  • IPPeak
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • Kookey
  • LemonBright
  • LightningProxies
  • MangoProxy
  • MoMoProxy
  • NSocks
  • NextProxy
  • NiuProxy
  • NodeProxy
  • NovaProxy
  • Novada
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • PuraRoute
  • RainProxy
  • RapidProxy
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • TORCHPROXIES_PREMIUM
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.10.0.0/17
since Apr 2016
AS8866Residential1,470
68 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.32.0/198,192BTC-BROADBAND-NET-98BTC Broadband ServiceASSIGNED PAJul 13, 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
Dec 2010
Current origin since
Dec 2010 · 16 yr
Origin networks
1