5.252.56.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 |
|---|---|---|---|---|---|
| AS31221 nLighten France SAS | no ROA | 43 | 345492907531221 | 2026-09-18 | 2026-09-20 |
| AS209468 nLighten France SAS | no ROA | 1 | 3800134913356209468 | 2026-09-18 | 2026-09-20 |
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
- 5.252.56.0/22
- RIR
- RIPENCC
- Country
- 🇫🇷 FR
- Status
- allocated
- Allocated
- 2019-02-04
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
1 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 5.252.57.0/24 v4 | AS31221 nLighten France SAS | no ROA | 44 | 2026-09-18 |