Kalaam-Telecom

BGP inherited
Cluster stats
Netblocks10 · 2,846 IPv4 addresses
Registered in Saudi Arabia (7) · BH (3)
All fragments 147 blocks across 5 clusters
Cluster ID209140561
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
77.92.168.0/21 KALAAM-TELECOM RIPE ASSIGNED PA ● low
87.236.48.0/24 KALAAM-TELECOM RIPE ASSIGNED PA ● low
87.236.52.0/24 KALAAM-TELECOM RIPE ASSIGNED PA ● low
88.85.235.56/29 Kalaam-Telecom RIPE ASSIGNED PA ● low
88.85.245.144/29 Kalaam-Telecom RIPE ASSIGNED PA ● low
91.220.94.0 – 91.220.94.128 Kalaam-Telecom RIPE ASSIGNED PA ● low
91.220.94.129 – 91.220.94.255 Kalaam-Telecom RIPE ASSIGNED PA ● low
176.98.32.240/28 Kalaam-Telecom RIPE ASSIGNED PA ● low
178.20.145.172/30 Kalaam-Telecom RIPE ASSIGNED PA ● low
212.12.188.116/30 Kalaam-Telecom RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

DUMY-RIPE DUMY-RIPE KTBB-MNT KTKSA-MNT NOURNET-MNT SAMEH