212.220.222.0/23 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
AS6828 PJSC Rostelecom	RPKI valid	6	34927 5405 12389 6828	2026-09-18	2026-11-05
AS65343	RPKI invalid	1	38001 7473 12389 6828 65343	2026-09-18	2026-11-05

RPKI

4 ROAs cover this prefix

ROA prefix	Max length	Authorised origin	Trust anchor	Result for this route
212.220.222.0/23	/23	AS6828	ripe	authorises it
212.220.222.0/23	/23	AS12389	ripe	wrong origin
212.220.192.0/19	/19	AS12389	ripe	wrong origin
212.220.0.0/16	/16	AS12389	ripe	wrong origin

Registry

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

Delegated block: 212.220.0.0/16
RIR: RIPENCC
Country: 🇷🇺 RU
Status: allocated
Allocated: 1998-03-11

Less specific routes

Announced prefixes that contain this one

Prefix	Origin	RPKI	Peers	Sample path	First seen
212.220.192.0/19 v4	AS12389 PJSC Rostelecom	RPKI valid	44	24482 12389	2026-09-18
212.220.0.0/16 v4	AS12389 PJSC Rostelecom	RPKI valid	44	24482 12389	2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.