185.67.165.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
AS40966 ZAO Web Hosting RPKI valid 35 3772140966 2026-09-18 2026-09-18
AS64249 Charles River Operation RPKI valid 7 2265212992755264249 2026-09-18 2026-09-18

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
185.67.165.0/24 /24 AS40966 ripe authorises it
185.67.165.0/24 /24 AS64249 ripe wrong origin
185.67.164.0/22 /22 AS40966 ripe too specific
185.67.164.0/22 /22 AS64249 ripe wrong origin

Registry

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

Delegated block
185.67.164.0/22
RIR
RIPENCC
Country
🇷🇺 RU
Status
allocated
Allocated
2014-08-19

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
185.67.164.0/22 v4 AS40966 ZAO Web Hosting RPKI valid 42 345492048540966 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 04:53:00Z origin change AS64249 → AS40966 20236550673321640966
2026-09-18 04:32:28Z origin change AS64249 → AS40966 20236550673321640966