200.220.202.0/24 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 41 377213746822381 2026-09-18 2026-10-13
AS262589 SAMM (Internexa) RPKI valid 1 24482262589 2026-09-18 2026-10-13

RPKI

2 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
200.220.192.0/20 /32 AS22381 lacnic authorises it
200.220.192.0/19 /32 AS262589 lacnic wrong origin

Registry

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

Delegated block
200.220.192.0/20
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2003-09-18

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
200.220.192.0/19 v4 AS262589 SAMM (Internexa) RPKI valid 3 37721262589 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:12Z origin change AS262589 → AS22381 1490733561295622381
2026-09-29 17:50:56Z origin change AS22381 → AS262589 24482262589
2026-09-29 17:35:22Z origin change AS262589 → AS22381 349275665512991295622381
2026-09-29 17:35:19Z origin change AS22381 → AS262589 24482262589