217.169.196.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
AS19905 Arbor Cloud RPKI valid 43 34549291419905 2026-09-18 2026-09-20
AS12794 AKBANK TAS RPKI valid 1 208972912112794 2026-09-18 2026-09-20

RPKI

5 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
217.169.196.0/24 /24 AS12794 ripe wrong origin
217.169.196.0/24 /24 AS19905 ripe authorises it
217.169.192.0/21 /21 AS12794 ripe wrong origin
217.169.192.0/20 /24 AS12794 ripe wrong origin
217.169.192.0/20 /24 AS19905 ripe authorises it

Registry

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

Delegated block
217.169.192.0/20
RIR
RIPENCC
Country
🇹🇷 TR
Status
allocated
Allocated
2001-03-27

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
217.169.192.0/21 v4 AS12794 AKBANK TAS RPKI valid 42 3772167623498412794 2026-09-18
217.169.192.0/20 v4 AS12794 AKBANK TAS RPKI valid 42 377216939912112794 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.