181.119.118.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 |
|---|---|---|---|---|---|
| AS18747 IFX Corporation | no ROA | 39 | 34549291418747 | 2026-09-24 | 2026-10-21 |
| AS52468 UFINET PANAMA S.A. | no ROA | 4 | 3772152468 | 2026-09-18 | 2026-10-21 |
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
- 181.119.0.0/16
- RIR
- LACNIC
- Country
- 🇦🇷 AR
- Status
- allocated
- Allocated
- 2012-08-20
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 181.119.0.0/17 v4 | AS18747 IFX Corporation | no ROA | 42 | 34549291418747 | 2026-09-18 |
| 181.119.0.0/16 v4 | AS18747 IFX Corporation | no ROA | 42 | 34549291418747 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.