185.218.7.0/24 RPKI valid 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
AS51089 SnapStack Limited RPKI valid 2 244824137851089 2026-09-18 2026-09-19
AS210110 Kvmcloud Network CO., LIMITED RPKI valid 1 443933571010099210110 2026-09-18 2026-09-19

RPKI

6 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
185.218.7.0/24 /24 AS51089 ripe authorises it
185.218.6.0/23 /23 AS51089 ripe too specific
185.218.4.0/22 /24 AS41378 ripe wrong origin
185.218.4.0/22 /24 AS51089 ripe authorises it
185.218.4.0/22 /24 AS60024 ripe wrong origin
185.218.4.0/22 /24 AS210110 ripe wrong origin

Registry

Who this address space is delegated to, regardless of whether it is routed

Delegated block
185.218.4.0/22
RIR
RIPENCC
Country
🇦🇺 AU
Status
allocated
Allocated
2017-08-17

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
185.218.6.0/23 v4 AS51089 SnapStack Limited RPKI valid 39 24482362364137851089 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.