163.237.210.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 |
|---|---|---|---|---|---|
| AS19255 YOUR.ORG, INC. | no ROA | 29 | 3454929142335219255 | 2026-09-18 | 2026-10-13 |
| AS13331 MetaPeer | no ROA | 13 | 244821925513331 | 2026-09-18 | 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
- 163.237.0.0/16
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1992-09-09
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 163.237.0.0/16 v4 | AS19255 YOUR.ORG, INC. | no ROA | 43 | 2448219255 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.