162.212.244.0/22 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 |
|---|---|---|---|---|---|
| AS40763 NUSO | no ROA | 27 | 701870140763 | 2026-10-09 | 2026-11-13 |
| AS394851 NUSO | no ROA | 15 | 380013491701394851 | 2026-09-18 | 2026-11-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.212.244.0/22
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2013-05-28
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 |
|---|---|---|---|---|
| 162.212.244.0/24 v4 | AS40763 NUSO | no ROA | 42 | 2026-09-18 |
| 162.212.245.0/24 v4 | AS40763 NUSO | no ROA | 42 | 2026-09-18 |
| 162.212.246.0/24 v4 | AS394851 NUSO | no ROA | 41 | 2026-09-18 |
| 162.212.247.0/24 v4 | AS394851 NUSO | no ROA | 41 | 2026-09-18 |