Data as of Nov 11, 2026

46.40.64.0/18

25 residential-proxy exits · 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential
95% of it
Recent change
New origin Aug 2026
from AS43205 Vivacom Bulgaria EAD

Residential-proxy exits

Proxy exits
25
0.15% of its addresses · 30 days
Always-on exits
1
4.0% of its exits
Spread
5 of 64
/24s with at least one exit
Providers
39
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

4.8K observations

/24s with the most always-on exits

Proxy providers listing exits

  • 9Proxy
  • Ake.net
  • AnyIP
  • BestProxy
  • BlurPath
  • BottingTools
  • Bright Data
  • Byteful
  • CliProxy
  • DataImpulse
  • Decodo
  • EZProxies
  • Evomi
  • FastProxy
  • FloppyData
  • GSocks
  • Geonode
  • IPFly
  • IPPeak
  • InfiniteProxies
  • KocerRoxy
  • LemonBright
  • NSocks
  • NiuProxy
  • NovaProxy
  • Oxylabs
  • PrivateByte
  • Proxiware
  • Proxy4U
  • ProxyGeo
  • ProxyRack
  • PuraRoute
  • RainProxy
  • RealProxy
  • Shifter
  • Smartproxy
  • Thordata
  • ThunderProxy
  • VitalExclusive

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
46.40.72.0/24
since May 2026
AS8866Internet providerVivacom Bulgaria EAD
46.40.75.0/24
since Apr 2026
AS43205ResidentialVivacom Bulgaria EAD
46.40.124.0/22
since Feb 2026
AS8866Residential24
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.40.64.0/1816,384BG-BTC-20100630Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAJun 30, 2010abuse-ip@vivacom.bg
└ 46.40.64.0/221,024BULSATCOM-INFRASTRUCTUREBulsatcom EADASSIGNED PAJun 30, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.68.0/221,024BULSATCOM-INFRASTRUCTUREBulsatcom EADASSIGNED PAJun 30, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.72.0/24256BULSATCOM-INFRASTRUCTUREBulsatcom EADASSIGNED PAJun 30, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.73.0/24256BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PAJul 8, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.74.0/24256BULSATCOMBulsatcom EADASSIGNED PAAug 4, 2015abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.75.0/24256BULSATCOM-CDNBulsatcom EADASSIGNED PAMar 11, 2019abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.76.0/221,024BULSATCOMBulsatcom MobileASSIGNED PAJul 8, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.84.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAApr 3, 2019abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.85.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PANov 11, 2020abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.86.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PANov 11, 2020abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.87.0/24256BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PANov 15, 2011abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.88.0/24256BULSATCOMBulsatcom EADASSIGNED PAFeb 17, 2015abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.90.0/23512BULSATCOMBulsatcom EADASSIGNED PAApr 19, 2017abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.92.0/23512BULSATCOMBulsatcom EOODASSIGNED PAJul 17, 2024abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.94.0/23512BULSATCOMBulsatcom EADASSIGNED PAFeb 9, 2017abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.96.0/212,048BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PANov 11, 2020abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.112.0/221,024BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAJul 15, 2021abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.116.0/221,024BULSATCOMBulsatcom ADASSIGNED PAAug 23, 2013abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.121.0/25128BULSATCOMBulsatcom ADASSIGNED PADec 3, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.121.128/25128BULSATCOMBulsatcom EADASSIGNED PAAug 10, 2017abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.122.0/24256BULGARIA-SATBulgaria Sat ADASSIGNED PAApr 4, 2016abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.123.0/25128BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PAOct 11, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.123.128/2732BULSATCOM-INFRASTRUCTUREBulsatcom EADASSIGNED PAJan 14, 2011abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.123.160/298BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PADec 28, 2011abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.123.168/298BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PAFeb 10, 2011abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.123.176/2816BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PAOct 11, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.123.192/2664BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PAOct 11, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.124.0/24256BULSATCOMBulsatcom ADASSIGNED PAMar 8, 2011abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.125.0/24256BULSATCOMBulsatcom ADASSIGNED PAMar 8, 2011abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.126.0/24256BULSATCOMBulsatcom ADASSIGNED PANov 25, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630
└ 46.40.127.0/24256BULSATCOMBulsatcom ADASSIGNED PAOct 11, 2010abuse-ip@vivacom.bg
via BG-BTC-20100630

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Composition

The types across the prefix's announced space, by addresses.

Announced space

Address share

Announced space

Types across the prefix

16,384 addresses
TypeAddressesShareRanges
Residential15,61695%6
Business5123.1%8
Internet provider2561.6%1

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Jul 2010
Current origin since
Aug 2026 · 3 mo
Origin networks
2
Last change of origin
Aug 2026
Recorded history

History

Handoffs
1