MTN SA
MTNSA-197-67-128-0-17
BGP inherited
Cluster stats
| Netblocks | 1 |
| All fragments | 2 blocks across 2 clusters |
| Cluster ID | 207314322 |
| Registry | AFRINIC |
| 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 (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 197.67.128.0/17 | MTNSA-197-67-128-0-17 | AFRINIC | ASSIGNED PA | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MTNSA 197 67” — 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.
- MTNSA-197-67-0-0-17 1 blocks
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.
- MTNSA-197-64-0-0-17 via MTN SA sub-allocation
- MTNSA-197-64-128-0-17 via MTN SA sub-allocation
- MTNSA-197-65-0-0-17 via MTN SA sub-allocation
- MTNSA-197-66-128-0-17 via MTN SA sub-allocation
- MTNSA-197-67-0-0-17 via MTN SA sub-allocation
- MTNSA-197-68-128-0-17 via MTN SA sub-allocation
- MTNSA-197-69-0-0-17 via MTN SA sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
RPKI-inferred operator
MTN SA
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
MBIP-AFRINIC
MBIP-AFRINIC
MTNBUSINESS-MNT