2409:8c85:5432::/48 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 |
|---|---|---|---|---|---|
| AS9808 China Mobile Backbone | no ROA | 32 | 24482584539808 | 2026-11-05 | 2026-11-05 |
| AS2010 INFONET Services Corporation | no ROA | 1 | 333369395845398082010 | 2026-09-18 | 2026-11-05 |
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
- 2409:8000::/20
- RIR
- APNIC
- Country
- 🇨🇳 CN
- Status
- allocated
- Allocated
- 2011-08-23
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 2409:8000::/20 v6 | AS9808 China Mobile Backbone | no ROA | 32 | 24482584539808 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.