64.9.97.0/24 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 |
|---|---|---|---|---|---|
| AS10753 Level 3 Parent, LLC | no ROA | 43 | 37721335610753 | 2026-09-18 | 2026-10-02 |
| AS3356 Lumen (Level 3) | no ROA | 1 | 580573356 | 2026-09-18 | 2026-10-02 |
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
- 64.9.0.0/17
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1999-12-07
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 64.9.0.0/17 v4 | AS3356 Lumen (Level 3) | no ROA | 44 | 377213356 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.