72.5.161.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 |
|---|---|---|---|---|---|
| AS32475 Internap Holding LLC | no ROA | 23 | 5805717432475 | 2026-09-18 | 2026-10-09 |
| AS14636 Internap Holding LLC | no ROA | 21 | 3454918282424714636 | 2026-09-18 | 2026-10-09 |
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
- 72.5.160.0/22
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2004-09-30
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 72.5.160.0/23 v4 | AS14636 Internap Holding LLC | no ROA | 21 | 3454918282424714636 | 2026-09-18 |
| 72.5.160.0/23 v4 | AS32475 Internap Holding LLC | no ROA | 23 | 5805717432475 | 2026-09-18 |
| 72.5.160.0/21 v4 | AS14743 Unitas Global | no ROA | 43 | 34549182814743 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.