189.91.108.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 39 345493746822381 2026-09-18 2026-10-07
AS262589 SAMM (Internexa) RPKI valid 1 24482262589 2026-09-18 2026-10-07

RPKI

2 ROAs cover this prefix

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

Registry

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

Delegated block
189.91.96.0/19
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2008-04-22

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
189.91.96.0/20 v4 AS262589 SAMM (Internexa) RPKI valid 42 24482262589 2026-09-18
189.91.96.0/19 v4 AS262589 SAMM (Internexa) RPKI valid 42 24482262589 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-29 17:55:47Z origin change AS262589 → AS22381 1490729143746822381
2026-09-29 17:50:55Z origin change AS22381 → AS262589 24482262589
2026-09-29 17:38:05Z origin change AS262589 → AS22381 4608757529143746822381
2026-09-29 17:35:19Z origin change AS22381 → AS262589 24482262589