BDCOM

BGP inherited
Cluster stats
Netblocks6 · 518 IPv4 addresses
All fragments 184 blocks across 12 clusters
Cluster ID211994546
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 12 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
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-07-19

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.7.248.60/30 Bdcom APNIC ALLOCATED NON-PORTABLE ● low
103.7.249.64/30 BDCOM APNIC ASSIGNED NON-PORTABLE ● low
103.131.157.92/31 BDCOM APNIC ALLOCATED NON-PORTABLE ● low
103.131.157.94/31 BDCOM APNIC ALLOCATED NON-PORTABLE ● low
119.40.89.0/24 BDCOM APNIC ALLOCATED NON-PORTABLE ● low
119.40.91.0/24 BDCOM APNIC ALLOCATED NON-PORTABLE ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “BDCOM” — 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.
Combined view of all 12 name-family clusters →
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)
No discrepancies found among checked blocks.

NIC Handles

AB1190-AP AF575-AP AF576-AP BA329-AP BA329-AP FGLA2-AP FGLA2-AP FHLN1-AP FHLN1-AP MAINT-BD-BDCOM MAINT-FGL-BD MAINT-FIBERATHOME-BD