MOEFIRE-V6-202406-AP
Handle
Cluster stats
| Netblocks | 1 |
| All fragments | 18 blocks across 18 clusters |
| Cluster ID | 207274037 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | RIR handle |
| Shared handles | clustered on 7 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 |
|---|---|---|---|---|
| 2406:840:ee45::/48 | MOEFIRE-V6-202406-AP | APNIC | ALLOCATED NON-PORTABLE | ● high |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “MOEFIRE V6” — 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.
- MOEFIRE-V6-20241212 1 blocks
- MOEFIRE-V6-202401-AP 1 blocks
- MOEFIRE-V6-202402-AP 1 blocks
- MOEFIRE-V6-202404-AP 1 blocks
- MOEFIRE-V6-202403-AP 1 blocks
- MOEFIRE-V6-202405-AP 1 blocks
- MOEFIRE-V6-202408-AP 1 blocks
- MOEFIRE-V6-20241210 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.
- MOEFIRE-V6-20241210 via Lin Siqi 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
Lin Siqi
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
AM4066-AP
LS2148-AP
LS2148-AP
MAINT-MOEFIRE-CN
MAINT-NBDHM-CN
ZR982-AP
ZZ3879-AP