Vivacom Bulgaria EAD-Bulsatcom

Data as of 2026-07-26
BGP inherited
Cluster stats
Netblocks6
IPv6 3 prefixes (largest 2001:7f8:58::a8c5:0:1/128)
All fragments 1,401 blocks across 2 clusters
Cluster ID214583607
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

6 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-26

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.1.30.33/32 Vivacom Bulgaria EAD-Bulsatcom PEERINGDB ASSIGNED ● high
185.1.40.28/32 Vivacom Bulgaria EAD-Bulsatcom PEERINGDB ASSIGNED ● high
193.169.198.224/32 Vivacom Bulgaria EAD-Bulsatcom PEERINGDB ASSIGNED ● high
2001:7f8:58::a8c5:0:1/128 Vivacom Bulgaria EAD-Bulsatcom PEERINGDB ASSIGNED ● high
2001:7f8:8e:4::33/128 Vivacom Bulgaria EAD-Bulsatcom PEERINGDB ASSIGNED ● high
2001:7f8:98::28/128 Vivacom Bulgaria EAD-Bulsatcom PEERINGDB ASSIGNED ● high

IPv6 ranges (3)

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS43205