31.206.56.0/21 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 AS	RPKI	Peers seeing it	Sample path	First seen	Last seen
AS15924 Vodafone Turkey	RPKI valid	43	34549 3257 15924	2026-09-18	2026-09-18
AS64639	RPKI invalid	1	208972 15924 64639	2026-09-18	2026-09-18

RPKI

2 ROAs cover this prefix

ROA prefix	Max length	Authorised origin	Trust anchor	Result for this route
31.206.56.0/21	/24	AS15924	ripe	authorises it
31.206.0.0/16	/16	AS15924	ripe	too specific

Registry

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

Delegated block: 31.206.0.0/16
RIR: RIPENCC
Country: 🇹🇷 TR
Status: allocated
Allocated: 2011-04-29

Less specific routes

Announced prefixes that contain this one

Prefix	Origin	RPKI	Peers	Sample path	First seen
31.206.0.0/16 v4	AS15924 Vodafone Turkey	RPKI valid	43	34549 3257 15924	2026-09-18
31.206.0.0/16 v4	AS64639	RPKI invalid	1	208972 15924 64639	2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

When	Change	Origin	Path
2026-09-18 07:14:23Z	origin change	AS64639 → AS15924	57381 50304 1299 3356 15924