MEGALOG-NET
Unresolved
Cluster stats
| Netblocks | 2 |
| All fragments | 19 blocks across 2 clusters |
| Cluster ID | 192382677 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 87.226.195.0/24 | MEGALOG-NET | RIPE | ASSIGNED PA | ● low |
| 91.143.24.0/22 | MEGALOG-NET | 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
(2 of 2)
Possible discrepancies (1)
These blocks are registered to MEGALOG-NET 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.
| 87.226.195.0/24 /24 | authorized for AS12389 — PJSC Rostelecom |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MEGALOG-MNT
ROSTELECOM-MNT