Xing Qingyu
YXOM_NETWORK-Wolverhampton
BGP inherited
Cluster stats
| Netblocks | 2 |
| All fragments | 9 blocks across 8 clusters |
| Cluster ID | 206305860 |
| 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 (2)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a06:9f81:4630::/44 | YXOM_NETWORK-Wolverhampton | RIPE | ASSIGNED | ● low |
| 2a14:67c2:700::/44 | YXOM_NETWORK-Wolverhampton | RIPE | ASSIGNED | ● low |
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
Xing Qingyu
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
YXOM-MNT