ORG-LL67-RIPE
Cluster stats
| Netblocks | 31 |
| All fragments | 903,420 blocks across 3,354 clusters |
| Cluster ID | 195630629 |
| 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 (31)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 5.172.194.0/24 | UNKNOWN | RIPE | SUB-ALLOCATED PA | ● high |
| 5.172.198.0/24 | UNKNOWN | RIPE | SUB-ALLOCATED PA | ● high |
| 5.172.194.101 – 5.172.194.103 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.194.105/32 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.194.173 – 5.172.194.179 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.194.186/32 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.194.188 – 5.172.194.206 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.194.208/30 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.198.0/27 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.198.33 – 5.172.198.54 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.198.56 – 5.172.198.83 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.199.0/24 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 5.172.201.0/24 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 45.66.185.0/24 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.169.0/24 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.170.0 – 178.21.170.128 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.170.129 – 178.21.170.255 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.171.0 – 178.21.171.47 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.171.61 – 178.21.171.69 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.171.71 – 178.21.171.83 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.171.85 – 178.21.171.93 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.171.95 – 178.21.171.100 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.171.102 – 178.21.171.113 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.175.0 – 178.21.175.8 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.175.10/31 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.175.13 – 178.21.175.94 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.175.96 – 178.21.175.239 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 178.21.175.241 – 178.21.175.255 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 185.70.76.0 – 185.70.76.26 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 185.70.76.28 – 185.70.76.128 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
| 185.70.76.129 – 185.70.76.255 | UNKNOWN | RIPE | ASSIGNED PA | ● medium |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(31 of 31)
Possible discrepancies (6)
These blocks are registered to ORG-LL67-RIPE 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.
| 5.172.198.0/24 /24 | authorized for AS199081 — Lancom Ltd. |
| 5.172.194.0/24 /24 | authorized for AS199081 — Lancom Ltd. |
| 5.172.199.0/24 /24 | authorized for AS199081 — Lancom Ltd. |
| 5.172.201.0/24 /24 | authorized for AS199081 — Lancom Ltd. |
| 178.21.169.0/24 /24 | authorized for AS199081 — Lancom Ltd. |
| 45.66.185.0/24 /24 | authorized for AS199081 — Lancom Ltd. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
MNT-LANCOM1