MRCSV
BGP inherited
Cluster stats
| Netblocks | 7 |
| Cluster ID | 208801980 |
| 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 | |
Footprint over time
5 weekly snapshots · JSON
7
0 netblocks since 2026-07-05
2026-07-05
peak 7
2026-07-19
IP Ranges (7)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.218.12.112/30 | MRCSV | RIPE | ASSIGNED PA | ● low |
| 89.218.151.64/30 | MRCSV | RIPE | ASSIGNED PA | ● low |
| 89.218.152.52/30 | MRCSV | RIPE | ASSIGNED PA | ● low |
| 89.218.156.32/30 | MRCSV | RIPE | ASSIGNED PA | ● low |
| 92.46.36.188/30 | MRCSV | RIPE | ASSIGNED PA | ● low |
| 95.56.245.152/30 | MRCSV | RIPE | ASSIGNED PA | ● low |
| 178.88.174.40/30 | MRCSV | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?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.
- MRCSVFILIALNAO via JSC Kazakhtelecom sub-allocation
- MRCSVAKT via JSC Kazakhtelecom sub-allocation
- MRCSVLEB via JSC Kazakhtelecom sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(7 of 7)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
KNIC-MNT