192.153.32.0/21 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 |
|---|---|---|---|---|---|
| AS600 OARnet | no ROA | 47 | 37721600 | 2026-09-18 | 2026-09-26 |
| AS3112 OARnet | no ROA | 1 | 3822924490115373112 | 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
- 192.153.32.0/21
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1992-03-31
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
2 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 192.153.32.0/24 v4 | AS600 OARnet | no ROA | 47 | 2026-09-18 |
| 192.153.34.0/24 v4 | AS36831 | no ROA | 46 | 2026-09-18 |