RuiNetwork-HK-Kivenxi2
Handle
Cluster stats
| Netblocks | 1 |
| All fragments | 3 blocks across 3 clusters |
| Cluster ID | 206343659 |
| Registry | RIPE |
| Customers | find customers using 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 | |
IP Ranges (1)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 2a14:67c1:b599::/48 | RuiNetwork-HK-Kivenxi2 | RIPE | ASSIGNED | ● medium |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “RuiNetwork HK” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- RuiNetwork-HK 1 blocks
- RuiNetwork-HK-MoeDove 1 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- Rui Network HK via Rui Feng sub-allocation
- Rui Network KP via Rui Feng sub-allocation
- Rui Network AQ via Rui Feng sub-allocation
- Rui Network HK2 via Liu HaoRan sub-allocation
- Rui Network CN Home via Axivora Connect Ltd sub-allocation
- Rui Network CX via Rui Feng sub-allocation
- Rui Network TW via Rui Feng sub-allocation
- Rui Network DE via Rui Feng sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(1 of 1)
RPKI-inferred operator
Rui Feng
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
RUI-FENG-MNT