130.120.0.0/16 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 |
|---|---|---|---|---|---|
| AS1715 Renater | no ROA | 42 | 3772122001715 | 2026-09-18 | 2026-10-16 |
| AS2200 Renater | no ROA | 1 | 2040922200 | 2026-09-18 | 2026-10-16 |
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
- 130.120.0.0/16
- RIR
- RIPENCC
- Country
- 🇫🇷 FR
- Status
- assigned
- Allocated
- 1993-09-01
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-15 13:49:30Z | origin change | AS2200 → AS1715 | 494324836226032132022001715 |
| 2026-10-15 13:35:04Z | origin change | AS1715 → AS2200 | 204092220022002200 |
| 2026-10-11 11:05:04Z | origin change | AS2200 → AS1715 | 244822200220022001715 |
| 2026-10-11 10:24:48Z | origin change | AS1715 → AS2200 | 204092220022002200 |