216.87.168.0/23 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 |
|---|---|---|---|---|---|
| AS3064 HDC/HW Enterprise, LLC | no ROA | 35 | 345491743064 | 2026-09-18 | 2026-09-26 |
| AS18447 HDC/HW Enterprise, LLC | no ROA | 6 | 149071915118447 | 2026-09-18 | 2026-09-26 |
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
- 216.87.160.0/19
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1999-07-21
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
4 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 216.87.168.0/24 v4 | AS3064 HDC/HW Enterprise, LLC | no ROA | 35 | 2026-09-18 |
| 216.87.168.0/24 v4 | AS18447 HDC/HW Enterprise, LLC | no ROA | 6 | 2026-09-18 |
| 216.87.169.0/24 v4 | AS3064 HDC/HW Enterprise, LLC | no ROA | 35 | 2026-09-18 |
| 216.87.169.0/24 v4 | AS18447 HDC/HW Enterprise, LLC | no ROA | 6 | 2026-09-18 |
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-09-23 20:15:32Z | origin change | AS18447 → AS3064 | 496731238933563064 |
| 2026-09-23 18:42:13Z | origin change | AS3064 → AS18447 | 14907191511915118447 |
| 2026-09-19 18:41:40Z | origin change | AS18447 → AS3064 | 3288403277271743064 |
| 2026-09-19 18:19:36Z | origin change | AS3064 → AS18447 | 5991990021915118447 |
| 2026-09-18 07:14:22Z | origin change | AS18447 → AS3064 | 5738150304129933563064 |