LAYER3 INTEL
Get started
Sign in
Data as of Nov 11, 2026

46.47.80.0/21

23 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
AS8866
Type
Residential
Risk
0 / 100 · Low

Residential-proxy exits

Proxy exits
23
1.1% of its addresses · 30 days
Spread
6 of 8
/24s with at least one exit
Providers
62
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2.2K observations

/24s with the most always-on exits

/24Always-on exitsProxy exits
46.47.81.0/2405
46.47.84.0/2405
46.47.80.0/2404
46.47.82.0/2404
46.47.87.0/2403
46.47.83.0/2402

Proxy providers listing exits

  • 2Captcha
  • 711Proxy
  • 911Proxy
  • ASHBURNPROXIES
  • Ake.net
  • AnyIP
  • BestProxy
  • BirdProxies
  • BottingTools
  • ByteProxies
  • Byteful
  • CliProxy
  • CoreProxy
  • DataImpulse
  • Decodo
  • EVOPROXY
  • EnigmaProxy
  • Evomi
  • FastProxy
  • FlashProxy
  • FlexyProxies
  • FloppyData
  • GeekProxy
  • GonzoProxy
  • IPOasis
  • IPRoyal
  • Infatica
  • KocerRoxy
  • LUMIPROXY
  • LemonBright
  • LightningProxies
  • MagneticProxy
  • MangoProxy
  • MarsProxies
  • NSocks
  • NiuProxy
  • NodeMaven
  • NodeProxy
  • NovaProxy
  • Oxylabs
  • PSBProxy
  • PrivateByte
  • Proxiware
  • Proxmint
  • Proxy-Seller
  • Proxy4U
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Q2IP
  • RainProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VProxy
  • VantageProxies
  • VibeProxies
  • VitalExclusive
  • VitalProxy
  • ZENPROXY_PREMIUM

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
46.47.64.0/18
since Jul 2026
AS8866Residential24Vivacom 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.47.64.0/1816,384BG-BTC-20101008Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAOct 8, 2010abuse-ip@vivacom.bg
└ 46.47.80.0/24256BULSATCOMBulsatcom ADASSIGNED PADec 2, 2011abuse-ip@vivacom.bg
via BG-BTC-20101008
└ 46.47.81.0/24256BULSATCOMBulsatcom ADASSIGNED PAFeb 28, 2012abuse-ip@vivacom.bg
via BG-BTC-20101008
└ 46.47.82.0/24256BULSATCOMBulsatcom ADASSIGNED PAFeb 28, 2012abuse-ip@vivacom.bg
via BG-BTC-20101008
└ 46.47.83.0/24256BULSATCOMBulsatcom ADASSIGNED PAFeb 28, 2012abuse-ip@vivacom.bg
via BG-BTC-20101008
└ 46.47.84.0/24256BULSATCOMBulsatcom EADASSIGNED PAFeb 17, 2015abuse-ip@vivacom.bg
via BG-BTC-20101008
└ 46.47.85.0/24256BULSATCOMBulsatcom EADASSIGNED PAFeb 17, 2015abuse-ip@vivacom.bg
via BG-BTC-20101008
└ 46.47.86.0/24256BULSATCOMBulsatcom EADASSIGNED PAFeb 17, 2015abuse-ip@vivacom.bg
via BG-BTC-20101008
└ 46.47.87.0/24256BULSATCOMBulsatcom EADASSIGNED PAFeb 17, 2015abuse-ip@vivacom.bg
via BG-BTC-20101008

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

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Feb 2026
Current origin since
Feb 2026 · 9 mo
Origin networks
1