2a03:9da0::/40 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
AS42831 UK Dedicated Servers Limited no ROA 27 5030042831 2026-09-18 2026-09-20
AS199741 TransitX Ltd no ROA 8 34549900235200199741 2026-09-18 2026-09-20

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
2a03:9da0::/32
RIR
RIPENCC
Country
🇬🇧 GB
Status
allocated
Allocated
2015-12-07

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-20 04:45:11Z origin change AS42831 → AS199741 3480029632900235200199741
2026-09-19 08:28:13Z origin change AS199741 → AS42831 29504693942831
2026-09-19 02:26:02Z origin change AS42831 → AS199741 4943248362900235200199741
2026-09-18 07:11:04Z origin change AS199741 → AS42831 57381693942831