109.234.200.0/21 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
AS31727 Node4 Limited no ROA 37 34549325731727 2026-09-18 2026-09-18
AS65539 Private Documentation ASN no ROA 3 5572069393172765539 2026-09-18 2026-09-18

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
109.234.200.0/21
RIR
RIPENCC
Country
🇬🇧 GB
Status
allocated
Allocated
2010-02-19

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

7 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
109.234.200.0/24 v4 AS31727 Node4 Limited no ROA 42 2026-09-18
109.234.202.0/24 v4 AS31727 Node4 Limited no ROA 42 2026-09-18
109.234.203.0/24 v4 AS31727 Node4 Limited no ROA 42 2026-09-18
109.234.204.0/24 v4 AS31727 Node4 Limited no ROA 42 2026-09-18
109.234.205.0/24 v4 AS31727 Node4 Limited no ROA 42 2026-09-18
109.234.206.0/24 v4 AS31727 Node4 Limited no ROA 42 2026-09-18
109.234.207.0/24 v4 AS31727 Node4 Limited no ROA 42 2026-09-18

Recorded changes

WhenChangeOriginPath
2026-09-18 13:43:07Z origin change AS31727 → AS65539 32884032772717431727317273172765539
2026-09-18 13:37:43Z origin change AS65539 → AS31727 37721325731727
2026-09-18 13:37:41Z origin change AS31727 → AS65539 5572069393172765539
2026-09-18 13:37:37Z origin change AS65539 → AS31727 33331103325731727
2026-09-18 13:37:36Z origin change AS31727 → AS65539 491345335669393172765539