STC BAHRAIN B.S.C CLOSED
MENA-CORE-2
BGP inherited
Cluster stats
| Netblocks | 4 |
| All fragments | 32 blocks across 2 clusters |
| Cluster ID | 204472390 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 3 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 109.63.64.0/19 | MENA-CORE-2 | RIPE | ASSIGNED PA | ● low |
| 109.63.96.0/19 | MENA-CORE-2 | RIPE | ASSIGNED PA | ● low |
| 178.132.32.0/21 | MENA-CORE-2 | RIPE | ASSIGNED PA | ● low |
| 178.132.40.0/21 | MENA-CORE-2 | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MENA CORE” — 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.
- MENA-CORE-1 28 blocks
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
RPKI-inferred operator
STC BAHRAIN B.S.C CLOSED
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
MENA-MNT