Baharan PLC

BGP inherited
Cluster stats
Netblocks8 · 3,065 IPv4 addresses
All fragments 9 blocks across 2 clusters
Cluster ID210864593
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.9.252.0/23 Baharan PLC BGP ANNOUNCED ● high
37.9.252.0/24 Baharan PLC BGP ANNOUNCED ● high
37.9.253.0/24 Baharan PLC BGP ANNOUNCED ● high
37.9.254.0/24 Baharan PLC BGP ANNOUNCED ● high
37.9.254.0/23 Baharan PLC BGP ANNOUNCED ● high
37.9.255.0/24 Baharan PLC BGP ANNOUNCED ● high
37.9.252.0/22 Baharan PLC RIPE ALLOCATED PA ● low
2a0a:3c40::/29 Baharan PLC RIPE ALLOCATED-BY-RIR ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Baharan” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

Network trust

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

NIC Handles

AS13231 Ashkan-mtn Ashkan-mtn DUMY-RIPE DUMY-RIPE ORG-BP37-RIPE RIPE-NCC-HM-MNT