46.148.255.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
AS49154 MTS PJSC no ROA 34 345491299835949154 2026-09-18 2026-09-22
AS65404 no ROA 5 333383594915465404 2026-09-18 2026-09-22

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
46.148.240.0/20
RIR
RIPENCC
Country
🇷🇺 RU
Status
allocated
Allocated
2010-12-06

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
46.148.240.0/20 v4 AS8359 MTS PJSC no ROA 41 33338359 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-22 11:37:10Z origin change AS65404 → AS49154 8521299835949154
2026-09-22 11:30:12Z origin change AS49154 → AS65404 55720693983594915465404
2026-09-18 07:14:26Z origin change AS65404 → AS49154 57381503041299835949154