84.252.160.0/19 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
AS208398 Edge Technology Plus (Yandex) RPKI valid 29 345491299208398 2026-09-18 2026-09-20
AS13238 YANDEX LLC RPKI valid 13 3772113238 2026-09-18 2026-09-20

RPKI

3 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
84.252.160.0/19 /24 AS13238 ripe wrong origin
84.252.160.0/19 /20 AS44534 ripe wrong origin
84.252.160.0/19 /24 AS208398 ripe authorises it

Registry

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

Delegated block
84.252.160.0/19
RIR
RIPENCC
Country
🇷🇺 RU
Status
allocated
Allocated
2004-09-16

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

2 announced prefixes inside this one

Prefix Origin RPKI Peers First seen
84.252.160.0/20 v4 AS44534 YANDEX LLC RPKI valid 42 2026-09-18
84.252.160.0/24 v4 AS44534 YANDEX LLC RPKI invalid 3 2026-09-18