43.224.244.0/22 no ROA MOAS
Announced by 2 different origins, which is either a deliberate multi-origin setup or a hijack.
This prefix is announced by more than one AS. Compare how many collector
peers see each origin below: a hijack is usually visible as a second
origin seen by far fewer peers than the legitimate one.
Origins
| Origin AS | RPKI | Peers seeing it | Sample path | First seen | Last seen |
|---|---|---|---|---|---|
| AS63915 XIAOMI H.K. Limited | no ROA | 22 | 34549930463915 | 2026-09-18 | 2026-10-15 |
| AS63855 XIAOMI H.K. Limited | no ROA | 21 | 38001349163855 | 2026-09-18 | 2026-10-15 |
RPKI
No ROA covers this prefix
No ROA covers this prefix, so origin validation returns "unknown". That is not a fault; most of the table is still unsigned.
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 43.224.244.0/22
- RIR
- APNIC
- Country
- ðŸ‡ðŸ‡° HK
- Status
- allocated
- Allocated
- 2014-11-27
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
2 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 43.224.244.0/23 v4 | AS63855 XIAOMI H.K. Limited | no ROA | 43 | 2026-09-18 |
| 43.224.246.0/23 v4 | AS63855 XIAOMI H.K. Limited | no ROA | 43 | 2026-09-18 |