217.117.32.0/19 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 |
|---|---|---|---|---|---|
| AS204013 Network Research Belgium S.A. | no ROA | 41 | 345491299204013 | 2026-09-18 | 2026-11-13 |
| AS12942 Network Research Belgium S.A. | no ROA | 1 | 32884032772717420401312942 | 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
No delegation record covers this prefix.
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
27 announced prefixes inside this one