RIPE-NCC-Manager
Data as of 2026-09-27
Handle
This organisation
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2a0e:b107:2130::/44) |
| Also registered under this name | 265 netblocks across 10 separate records |
| Record ID | 248546651 |
| Registry | RIPE |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 4 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0e:b107:2130::/44 | RIPE-NCC-Manager | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0e:b107:2510::/44 | RIPE-NCC-Manager | RIPE | ALLOCATED-BY-LIR | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(1 of 2)
RPKI-inferred operator
Alternate Access Inc.
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
ORG-NCC10-RIPE
SBMT