BOL-COM

Data as of 2026-10-04
Handle
This organisation
Netblocks12
IPv6 6 prefixes (largest 2001:7f8:13::a519:9408:1/128)
Record ID246693023
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution RIR handle
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

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.249.210.83/32 BOL-COM PEERINGDB ASSIGNED ● high
80.249.214.72/32 BOL-COM PEERINGDB ASSIGNED ● high
185.1.112.111/32 BOL-COM PEERINGDB ASSIGNED ● high
185.1.112.112/32 BOL-COM PEERINGDB ASSIGNED ● high
193.239.117.34/32 BOL-COM PEERINGDB ASSIGNED ● high
193.239.117.78/32 BOL-COM PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:19:9408:1/128 BOL-COM PEERINGDB ASSIGNED ● high
2001:7f8:1:0:a500:19:9408:2/128 BOL-COM PEERINGDB ASSIGNED ● high
2001:7f8:13::a519:9408:1/128 BOL-COM PEERINGDB ASSIGNED ● high
2001:7f8:13::a519:9408:2/128 BOL-COM PEERINGDB ASSIGNED ● high
2001:7f8:83::19:9408:1/128 BOL-COM PEERINGDB ASSIGNED ● high
2001:7f8:83::19:9408:2/128 BOL-COM PEERINGDB ASSIGNED ● high

IPv6 ranges (6)

Footprint over time

10 weekly snapshots · JSON
12 0 netblocks since 2026-07-26
2026-07-26 peak 12 2026-10-04

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (12 of 12)
No discrepancies found among checked blocks.

NIC Handles

AS199408