L66613
Cluster stats
| Netblocks | 16 |
| Cluster ID | 193001375 |
| 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 (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.173.93.188/30 | L66613 | RIPE | ASSIGNED PA | ● low |
| 80.168.27.224/28 | L66613 | RIPE | ASSIGNED PA | ● low |
| 81.171.194.60/31 | L66613 | RIPE | ASSIGNED PA | ● low |
| 89.206.140.45/32 | L66613 | RIPE | ASSIGNED PA | ● low |
| 89.206.171.240/30 | L66613 | RIPE | ASSIGNED PA | ● low |
| 89.206.176.232/30 | L66613 | RIPE | ASSIGNED PA | ● low |
| 89.206.198.144/30 | L66613 | RIPE | ASSIGNED PA | ● low |
| 89.206.220.192/26 | L66613 | RIPE | ASSIGNED PA | ● low |
| 213.165.150.80/28 | L66613 | RIPE | ASSIGNED PA | ● low |
| 213.165.150.96/28 | L66613 | RIPE | ASSIGNED PA | ● low |
| 213.165.154.0/24 | L66613 | RIPE | ASSIGNED PA | ● low |
| 213.253.35.96/27 | L66613 | RIPE | ASSIGNED PA | ● low |
| 217.158.17.248/29 | L66613 | RIPE | ASSIGNED PA | ● low |
| 217.158.84.10/32 | L66613 | RIPE | ASSIGNED PA | ● low |
| 217.158.135.204/31 | L66613 | RIPE | ASSIGNED PA | ● low |
| 217.158.238.32/28 | L66613 | 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
(16 of 16)
Possible discrepancies (1)
These blocks are registered to L66613 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.
| 213.165.154.0/24 /24 | authorized for AS8426 — Claranet Limited |
NIC Handles
AS8426-MNT
DUMY-RIPE
DUMY-RIPE