BRUEGGUS-AS_NL_5
Data as of 2026-07-26
BGP inherited
Cluster stats
| Netblocks | 2 |
| IPv6 | 2 prefixes (largest 2a06:a001:a07a::/47) |
| All fragments | 9 blocks across 7 clusters |
| Cluster ID | 216248216 |
| 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 · report an issue | |
IP Ranges (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a06:a001:a07a::/47 | BRUEGGUS-AS_NL_5 | RIPE | ASSIGNED | ● low |
| 2a14:7581:5fe::/48 | BRUEGGUS-AS_NL_5 | RIPE | ASSIGNED | ● low |
IPv6 ranges (2)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(2 of 2)
RPKI-inferred operator
Alexander Bruegmann
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
brueggus-mnt