212.19.149.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
AS50482 JSC Kazakhtelecom RPKI valid 42 3454931133919850482 2026-09-18 2026-09-21
AS9198 JSC Kazakhtelecom RPKI valid 2 377219198 2026-09-18 2026-09-21

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
212.19.149.0/24 /24 AS9198 ripe wrong origin
212.19.149.0/24 /24 AS50482 ripe authorises it
212.19.128.0/19 /19 AS9198 ripe wrong origin
212.19.128.0/19 /24 AS50482 ripe authorises it

Registry

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

Delegated block
212.19.128.0/19
RIR
RIPENCC
Country
🇰🇿 KZ
Status
allocated
Allocated
1998-05-25

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
212.19.128.0/19 v4 AS50482 JSC Kazakhtelecom RPKI valid 46 24482919850482 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 08:54:34Z origin change AS50482 → AS9198 244829198
2026-09-18 08:54:21Z origin change AS9198 → AS50482 45049669620485919850482
2026-09-18 06:50:14Z origin change AS9198 → AS50482 20409220485919850482
2026-09-18 06:49:27Z origin change AS50482 → AS9198 244829198
2026-09-18 06:42:32Z origin change AS50482 → AS9198 244829198
2026-09-18 06:42:32Z origin change AS9198 → AS50482 2448243727919850482