AS39273 Kalaam-Telecom Kalaam Telecom Bahrain B.S.C.
π§πOrg handle: ORG-KTBB1-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
78total
75 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)30,464
Announced (BGP)30,208
IPv6 Addresses
Allocated (RIR)1.2Γ10Β³β°
Announced (BGP)1.3Γ10Β³β°
Prefix Limit (IPv4)
200
Prefix Limit (IPv6)
10
Country
π§π BHRIR
RIPE NCCStatus
allocated
Allocated
2006-01-23
Announced Prefixes
(BGP)78|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
77.83.88.0/22MOAS | Invalid | - | 2026-10-11 |
77.83.88.0/24MOAS | Invalid | - | 2026-10-11 |
77.83.89.0/24MOAS | Invalid | - | 2026-10-11 |
77.83.91.0/24MOAS | Invalid | - | 2026-10-11 |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 78
1 / 8
Allocated Prefixes
(RIR)46Prefix | Country | RIR | Status |
|---|---|---|---|
| 77.83.88.0/22 | πΈπ¦ SA | RIPENCC | allocated |
| 77.83.88.0/24 | π§π BH | RIPE | assigned |
| 77.83.89.0/24 | π§π BH | RIPE | assigned |
| 77.83.90.0/24 | π§π BH | RIPE | assigned |
| 77.83.91.0/24 | π§π BH | RIPE | assigned |
| 77.92.168.0/21 | π§π BH | RIPENCC | allocated |
| 77.92.176.0/20 | π§π BH | RIPENCC | allocated |
| 77.92.176.0/22 | π§π BH | RIPENCC | allocated |
| 77.92.180.0/24 | πΈπ¦ SA | RIPE | assigned |
| 77.92.181.0/24 | πΈπ¦ SA | RIPE | assigned |
1-10 of 46
1 / 5
All 78 announced prefixes of AS39273 β
BGP Neighbours
(seen in AS paths)Upstreams (4)
Networks AS39273 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (4)
Networks whose own prefixes AS39273 passes on: usually its customers.
Other adjacent networks (1)
Adjacent to AS39273 in the transit part of AS paths: peers, providers or customers.
- AS8529OMANTEL Zain Omantel International FZ2
ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS39273 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/39273Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/39273" | jq