KRASNET-LRC
Cluster stats
| Netblocks | 19 |
| All fragments | 38 blocks across 12 clusters |
| Cluster ID | 191912061 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| 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 (19)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 195.112.224.0 – 195.112.227.63 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.227.64/27 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.227.128/27 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.227.192 – 195.112.227.215 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.227.216 – 195.112.227.251 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.231.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.234.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.237.0 – 195.112.237.251 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.239.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.240.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.242.0/23 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.244.0/23 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.246.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.247.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.248.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.249.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.252.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.254.0/24 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
| 195.112.255.64 – 195.112.255.255 | KRASNET-LRC | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(19 of 19)
Possible discrepancies (13)
These blocks are registered to KRASNET-LRC but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 195.112.224.0 – 195.112.227.63 /22 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.242.0/23 /23 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.244.0/23 /23 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.231.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.240.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.246.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.248.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.254.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.252.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.234.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.247.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.239.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
| 195.112.249.0/24 /24 | authorized for AS5573 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
ROSTELECOM-MNT