Data as of Nov 19, 2026

46.10.189.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
66
selling exits here
Oct 20, 2026 – Nov 18, 2026

Exits seen per day

8.2K observations

Proxy providers listing exits

  • 711Proxy
  • 9HTTP
  • 9Proxy
  • AETHYN_ELITE
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BartProxies
  • BestProxy
  • BirdProxies
  • BottingTools
  • Byteful
  • CROXY
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FLAMEPROXIES_BASIC
  • FLAMEPROXIES_PREMIUM
  • FastProxy
  • FlexyProxies
  • GEEKPROXY_FLEX
  • GEEKPROXY_TURBO
  • GSocks
  • Geonix
  • Geonode
  • GloryCloud
  • IPMUSK
  • IPPeak
  • IPROCKET_PREMIUM
  • IPRoyal
  • Infatica
  • InfiniteProxies
  • KindProxy
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • MangoProxy
  • NSocks
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PROXYLANE
  • PROXYSCRAPE
  • PrivateProxy
  • Proxies.fo
  • Proxiware
  • Proxy-Seller
  • Proxy302
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • Proxyma
  • RainProxy
  • RapidProxy
  • SOTAPROXY
  • Shifter
  • Smartproxy
  • SwiftProxy
  • TORCHPROXIES_BASIC
  • Thordata
  • ThunderProxy
  • VantageProxies
  • VitalExclusive
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.10.184.0/21
since Oct 2016
AS8866Residential133
4 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.184.0 - 46.10.189.2551,536BTC-BROADBAND-NET-15unknownASSIGNED PAApr 19, 2019abuse-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
Aug 2021
Current origin since
Aug 2021 · 5.3 yr
Origin networks
1