2a02:e340::/32 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
AS50304 Blix Solutions AS RPKI valid 35 2448250304 2026-09-18 2026-09-19
AS64526 RPKI invalid 2 64526 2026-09-18 2026-09-19

RPKI

1 ROA covers this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
2a02:e340::/29 /48 AS50304 ripe authorises it

Registry

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

Delegated block
2a02:e340::/29
RIR
RIPENCC
Country
🇳🇴 NO
Status
allocated
Allocated
2012-11-16

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 07:43:51Z origin change AS64526 → AS50304 202365693950304
2026-09-18 07:42:50Z origin change AS50304 → AS64526 573815030464526
2026-09-18 07:13:17Z origin change AS64526 → AS50304 202365693950304
2026-09-18 07:11:04Z origin change AS50304 → AS64526 573815030464526
2026-09-18 06:38:04Z origin change AS64526 → AS50304 202365693950304
2026-09-18 06:36:49Z origin change AS50304 → AS64526 573815030464526
2026-09-18 04:39:46Z origin change AS64526 → AS50304 202365693950304
2026-09-18 04:29:42Z origin change AS64526 → AS50304 202365693950304
2026-09-18 04:20:44Z origin change AS64526 → AS50304 202365693950304
2026-09-18 04:08:32Z origin change AS64526 → AS50304 202365693950304