BH TELECOM
Cluster stats
Netblocks16
All fragments 157 blocks across 2 clusters
Cluster ID193385760
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
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

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
149.112.134.8/32 BH TELECOM PEERINGDB ASSIGNED ● high
206.41.104.108/32 BH TELECOM PEERINGDB ASSIGNED ● high
206.71.11.26/32 BH TELECOM PEERINGDB ASSIGNED ● high
206.72.208.39/32 BH TELECOM PEERINGDB ASSIGNED ● high
206.81.80.15/32 BH TELECOM PEERINGDB ASSIGNED ● high
206.82.110.21/32 BH TELECOM PEERINGDB ASSIGNED ● high
206.108.35.189/32 BH TELECOM PEERINGDB ASSIGNED ● high
206.108.255.194/32 BH TELECOM PEERINGDB ASSIGNED ● high
2001:504:16::4c43/128 BH TELECOM PEERINGDB ASSIGNED ● high
2001:504:1a::35:189/128 BH TELECOM PEERINGDB ASSIGNED ● high
2001:504:26::1:9523:1/128 BH TELECOM PEERINGDB ASSIGNED ● high
2001:504:27::4c43:0:1/128 BH TELECOM PEERINGDB ASSIGNED ● high
2001:504:39::108/128 BH TELECOM PEERINGDB ASSIGNED ● high
2001:504:69:8000::1400/128 BH TELECOM PEERINGDB ASSIGNED ● high
2001:504:96::110:21/128 BH TELECOM PEERINGDB ASSIGNED ● high
2602:f777:400::134:8/128 BH TELECOM PEERINGDB ASSIGNED ● high

Network trust

what's this?
RPKI hygiene: B how networks compare →
81.2% of checked blocks have valid RPKI ROA coverage (13 of 16)
No discrepancies found among checked blocks.

NIC Handles

AS19523