LepidaSPA-NET
BGP inherited
Cluster stats
| Netblocks | 7 · 713 IPv4 addresses |
| All fragments | 9 blocks across 2 clusters |
| Cluster ID | 208826955 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names 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 |
|---|---|---|---|---|
| 80.21.108.108/30 | LEPIDASPA | RIPE | ASSIGNED PA | ● low |
| 80.23.108.40/30 | LEPIDASPA | RIPE | ASSIGNED PA | ● low |
| 195.62.164.0/24 | LepidaSPA-NET | RIPE | ASSIGNED PA | ● low |
| 195.62.178.192/26 | LepidaSPA-NET | RIPE | ASSIGNED PA | ● low |
| 195.62.186.0/24 | LepidaSPA-NET | RIPE | ASSIGNED PA | ● low |
| 195.62.190.0/25 | LepidaSPA-NET | RIPE | ASSIGNED PA | ● low |
| 195.120.11.40/29 | LEPIDASPA | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “LepidaSPA” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- LepidaSpA-dummy 2 blocks
Network trust
what's this?
RPKI hygiene: C
how networks compare →
57.1%
of checked blocks have valid RPKI ROA coverage
(4 of 7)
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
INTERB-MNT
LEPIDA-MNT