85.172.171.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 AS	RPKI	Peers seeing it	Sample path	First seen	Last seen
AS42610 PJSC Rostelecom	RPKI valid	7	34927 56655 12389 42610	2026-09-18	2026-09-26
AS64512 Private ASN	RPKI invalid	1	38001 7473 12389 42610 64512	2026-09-18	2026-09-26

RPKI

3 ROAs cover this prefix

ROA prefix	Max length	Authorised origin	Trust anchor	Result for this route
85.172.171.0/24	/24	AS42610	ripe	authorises it
85.172.168.0/22	/22	AS33934	ripe	wrong origin
85.172.0.0/14	/24	AS12389	ripe	wrong origin

Registry

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

Delegated block: 85.172.0.0/14
RIR: RIPENCC
Country: 🇷🇺 RU
Status: allocated
Allocated: 2004-12-22

Less specific routes

Announced prefixes that contain this one

Prefix	Origin	RPKI	Peers	Sample path	First seen
85.172.168.0/22 v4	AS33934 PJSC Rostelecom	RPKI valid	40	24482 12389 33934	2026-09-18
85.172.0.0/14 v4	AS12389 Rostelecom PJSC	RPKI valid	41	24482 12389	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-19 08:30:31Z	origin change	AS64512 → AS42610	29504 39392 33891 12389 42610