91.199.63.0/24 no ROA 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
AS31264 ADVANIA NORGE AS no ROA 38 244822969531264 2026-09-18 2026-09-30
AS64927 no ROA 1 557206939254003126464927 2026-09-18 2026-09-30

RPKI

No ROA covers this prefix

No ROA covers this prefix, so origin validation returns "unknown". That is not a fault; most of the table is still unsigned.

Registry

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

Delegated block
91.199.63.0/24
RIR
RIPENCC
Country
🇳🇴 NO
Status
assigned
Allocated
2007-12-05

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-29 17:41:20Z origin change AS64927 → AS31264 17639349112992540031264
2026-09-29 17:08:06Z origin change AS31264 → AS64927 557206939254003126464927
2026-09-28 21:23:03Z origin change AS64927 → AS31264 1763917412992540031264
2026-09-28 21:21:43Z origin change AS31264 → AS64927 557206939254003126464927
2026-09-22 11:37:42Z origin change AS64927 → AS31264 85212992540031264
2026-09-22 11:29:15Z origin change AS31264 → AS64927 557206939254003126464927
2026-09-18 04:44:39Z origin change AS64927 → AS31264 17639349112992540031264
2026-09-18 04:07:34Z origin change AS64927 → AS31264 17639349112992540031264