LIMA-1
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 208427268 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.90.36.108/30 | LIMA-1 | RIPE | ASSIGNED PA | ● low |
| 62.90.36.112/30 | LIMA-1 | RIPE | ASSIGNED PA | ● low |
| 82.166.9.48/30 | LIMA-1 | RIPE | ASSIGNED PA | ● low |
| 82.166.9.52/30 | LIMA-1 | RIPE | ASSIGNED PA | ● low |
Possibly related to this organisation
what's this?Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- HSVKLIMA-1 sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
No discrepancies found among checked blocks.
NIC Handles
BARAK-MNT
DUMY-RIPE
DUMY-RIPE