2804:368:900::/48 RPKI valid 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 ASRPKI Peers seeing itSample path First seenLast seen
AS22381 SAMM (Megatelecom) RPKI valid 32 37721693922381 2026-09-18 2026-10-02
AS262589 SAMM (Internexa) RPKI valid 1 24482262589 2026-09-30 2026-10-02

RPKI

3 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
2804:368::/32 /128 AS22381 lacnic authorises it
2804:368::/32 /128 AS28330 lacnic wrong origin
2804:368::/32 /128 AS262589 lacnic wrong origin

Registry

Who this address space is delegated to, regardless of whether it is routed

Delegated block
2804:368::/32
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2011-01-04

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2804:368::/32 v6 AS22381 SAMM (Megatelecom) RPKI valid 36 2448222381 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-29 18:02:43Z origin change AS262589 → AS22381 48185335622381
2026-09-29 17:50:35Z origin change AS22381 → AS262589 24482262589