31.7.172.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
AS200899 INTERSPACE DOOEL Skopje no ROA 39 34549200899 2026-09-18 2026-10-08
AS2008999 no ROA 4 3800190022008992008999 2026-09-18 2026-10-08

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
31.7.168.0/21
RIR
RIPENCC
Country
🇲🇰 MK
Status
allocated
Allocated
2011-04-14

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-10-08 22:36:53Z origin change AS200899 → AS2008999 58057183690022008992008992008999
2026-10-08 22:35:52Z origin change AS2008999 → AS200899 14035771299200899200899200899
2026-10-01 06:28:18Z origin change AS2008999 → AS200899 20236550673200899
2026-10-01 06:27:50Z origin change AS200899 → AS2008999 58057183690022008992008992008999
2026-09-28 21:22:45Z origin change AS2008999 → AS200899 557206939200899
2026-09-28 14:03:44Z origin change AS200899 → AS2008999 2162858280676290022008992008992008999
2026-09-25 13:02:03Z origin change AS2008999 → AS200899 8523257200899200899200899
2026-09-25 10:59:26Z origin change AS200899 → AS2008999 2162858280676290022008992008992008999