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

46.237.64.0/18

No anonymizer space · no proxy exits in 30 days

Vivacom Bulgaria EAD

Announcement
this exact prefix
RPKI valid
Announced by
AS8866
Type
Residential
95% of it
Recent change
New origin Jul 2026
from AS43205 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.237.64.0/1816,384BG-BTC-20110120Vivacom Bulgaria EAD (ORG-BTCP1-RIPE) · BGALLOCATED PAJan 20, 2011abuse-ip@vivacom.bg
└ 46.237.64.0/204,096BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAAug 2, 2022abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.80.0/221,024BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAJan 21, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.84.0/221,024BULSATCOMBulsatcom ADASSIGNED PAJan 21, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.92.0/221,024BULSATCOMBulsatcom ADASSIGNED PAOct 10, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.96.0/23512BULSATCOMBulsatcom EADASSIGNED PAMar 2, 2016abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.98.0/24256BULSATCOMBulsatcom EADASSIGNED PADec 15, 2015abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.99.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PASep 15, 2019abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.100.0/24256BULSATCOMBulsatcom EADASSIGNED PAJan 21, 2016abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.101.128/25128BULSATCOMBulsatcom ADASSIGNED PAApr 8, 2013abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.104.0/221,024BULSATCOMBulsatcom ADASSIGNED PAMar 7, 2012abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.108.0/25128BULSATCOMBulsatcom EADASSIGNED PAApr 4, 2016abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.109.0/25128BULSATCOMBulsatcom EADASSIGNED PAMar 12, 2016abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.110.0/23512BULSATCOM-CUSTOMERSBulsatcom EOODASSIGNED PAJul 16, 2024abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.112.0/23512BULSATCOMBulsatcom ADASSIGNED PAApr 14, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.114.0/24256BULSATCOMBulsatcom EADASSIGNED PAOct 20, 2017abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.115.0/25128BULSATCOMBulsatcom EADASSIGNED PADec 5, 2016abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.115.128/25128BULSATCOMBulsatcom EADASSIGNED PAJun 2, 2016abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.120.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PASep 15, 2019abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.121.0/24256BULSATCOMBulsatcom ADASSIGNED PADec 30, 2013abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.122.0/23512BULSATCOM-CUSTOMERSBulsatcom EOODASSIGNED PAJul 16, 2024abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.124.0/25128BULSATCOMBulsatcom EADASSIGNED PAJan 19, 2015abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.125.0/24256BULSATCOM-CUSTOMERSBulsatcom EADASSIGNED PAAug 24, 2018abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.0/298KSTunknownASSIGNED PAApr 21, 2015abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.8/298BULSATCOM-INFRASTRUCTUREBulsatcom EADASSIGNED PAMar 13, 2015abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.32/2732ID-SOFT-BGId Soft BG OODASSIGNED PAFeb 13, 2013abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.80/298FATUMFatum OODASSIGNED PAMay 15, 2018abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.88/298MS-HYDRAULICSMS HydraulicsASSIGNED PANov 9, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.96/2816CITY-LIBRARYCity LibraryASSIGNED PASep 28, 2017abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.208/2816BULSATCOM-INFRASTRUCTUREBulsatcom AD.ASSIGNED PAJul 1, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.232/298INFORMATION-SERVICES-YAMBOLInformation Services PLC, Yambol branchASSIGNED PAJul 4, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120
└ 46.237.127.240/2816BULSATCOM-INFRASTRUCTUREBulsatcom ADASSIGNED PAMay 3, 2011abuse-ip@vivacom.bg
via BG-BTC-20110120

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,49695%10
Business8885.4%15

Network & registry

AnnouncementRouting historyRPKI & IRRWhois & abuse
Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Rotating
First seen
Jan 2011
Current origin since
Jul 2026 · 4 mo
Origin networks
2
Last change of origin
Jul 2026
Recorded history

History

Handoffs
1