2804:680:20::/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 33 377211295622381 2026-09-18 2026-09-30
AS262589 SAMM (Internexa) RPKI valid 1 24482262589 2026-09-18 2026-09-30

RPKI

2 ROAs cover this prefix

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

Registry

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

Delegated block
2804:680::/32
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2011-09-19

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2804:680::/32 v6 AS22381 SAMM (Megatelecom) RPKI valid 33 50628335622381 2026-09-18
2804:680::/32 v6 AS262589 SAMM (Internexa) RPKI valid 1 37721262589 2026-09-24

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:56:50Z origin change AS22381 → AS262589 24482262589
2026-09-24 15:49:35Z origin change AS262589 → AS22381 5666225091335622381
2026-09-24 01:10:24Z origin change AS22381 → AS262589 24482262589
2026-09-18 05:35:33Z origin change AS262589 → AS22381 494324836290021295622381