NO-IOPS
Data as of 2026-09-06
Handle
This organisation
| Netblocks | 4 |
| IPv6 | 4 prefixes (largest 2a03:5580::/30) |
| Also registered under this name | 6 netblocks across 2 separate records |
| Record ID | 236485838 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| 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 · report an issue | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a03:5580::/30 | NO-IOPS | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a03:5580::/48 | NO-IOPS | RIPE | ASSIGNED | ● low |
| 2a03:5584::/30 | NO-IOPS | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a03:5584::/48 | NO-IOPS | RIPE | ASSIGNED | ● low |
IPv6 ranges (4)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
RPKI-inferred operator
Lindbak IT AS
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
DUMY-RIPE
DUMY-RIPE
IOPS-MNT