91.226.153.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
AS56677 Tele-Club Ltd. no ROA 41 3454912992048556677 2026-09-18 2026-10-11
AS65000 no ROA 1 24482204855667765000 2026-09-18 2026-10-11

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.226.152.0/22
RIR
RIPENCC
Country
🇷🇺 RU
Status
assigned
Allocated
2011-04-20

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:31:46Z origin change AS65000 → AS56677 3333125712991238956677
2026-10-08 22:28:27Z origin change AS56677 → AS65000 557206939204855667765000
2026-10-04 00:31:56Z origin change AS65000 → AS56677 61218693912731238956677
2026-10-03 22:03:18Z origin change AS56677 → AS65000 557206939204855667765000