193.43.15.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 |
|---|---|---|---|---|---|
| AS3313 RETELIT-X S.R.L. | no ROA | 37 | 3333540089683313 | 2026-09-18 | 2026-10-24 |
| AS198772 Costa Crociere S.p.a. | no ROA | 5 | 380018220198772 | 2026-09-18 | 2026-10-24 |
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
- 193.43.15.0/24
- RIR
- RIPENCC
- Country
- 🇮🇹 IT
- Status
- assigned
- Allocated
- 1994-07-12
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.