162.8.168.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 |
|---|---|---|---|---|---|
| AS3145 Refinitiv US LLC | no ROA | 43 | 70183145 | 2026-09-18 | 2026-10-13 |
| AS32067 Refinitiv US LLC | no ROA | 1 | 37989563001321324657645332067 | 2026-10-08 | 2026-10-13 |
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
- 162.8.0.0/16
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1992-06-25
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-10-07 16:20:15Z | origin change | AS32067 → AS3145 | 14907129933563145 |
| 2026-10-07 16:09:15Z | origin change | AS3145 → AS32067 | 37989563001321324657645332067320673206732067 |
| 2026-10-05 01:18:26Z | origin change | AS32067 → AS3145 | 20649934549291433563145 |
| 2026-10-05 00:27:37Z | origin change | AS3145 → AS32067 | 34549645332067320673206732067 |