Mubasher
mubasher
Registry
Cluster stats
| Netblocks | 6 |
| All fragments | 15 blocks across 2 clusters |
| Cluster ID | 210174641 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | Registry record |
| Shared handles | clustered on 3 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 |
|---|---|---|---|---|
| 5.42.237.88/30 | mubasher | RIPE | ASSIGNED PA | ● low |
| 87.101.130.8/30 | Mubasher | RIPE | ASSIGNED PA | ● low |
| 87.101.216.176/30 | mubasher | RIPE | ASSIGNED PA | ● low |
| 87.101.217.60/30 | mubasher | RIPE | ASSIGNED PA | ● low |
| 87.101.229.212/30 | Mubasher | RIPE | ASSIGNED PA | ● low |
| 128.127.225.128/29 | Mubasher | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “mubasher” — 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.
- Mubasher-ACS 9 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.
- Mubasher via E.G.I.T. for Technology Services sub-allocation
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
DUMY-RIPE
DUMY-RIPE
ITC-NOC-MNT