YUZU-Network
Data as of 2026-07-26
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 |
| IPv6 | 3 prefixes (largest 2a0a:d685:200::/40) |
| Cluster ID | 216418787 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 6 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a0a:d685:200::/40 | YUZU-Network | RIPE | ALLOCATED-BY-LIR | ● low |
| 2a0a:d685:200::/48 | YUZU-Network | RIPE | ASSIGNED | ● low |
| 2a0a:d685:201::/48 | YUZU-Network | RIPE | ASSIGNED | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
RPKI-inferred operator
Yunxiao Bai
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
LOCYAN-MNT
ORG-YA216-RIPE
SESS-MNT
YUZU-MNT