202.71.105.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
AS17971 TM TECHNOLOGY SERVICES SDN. BHD. RPKI valid 39 34549584531820617971 2026-09-18 2026-09-22
AS18206 TM TECHNOLOGY SERVICES SDN. BHD. RPKI valid 2 5572018206 2026-09-18 2026-09-22

RPKI

4 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
202.71.104.0/22 /24 AS17971 apnic authorises it
202.71.104.0/22 /24 AS18206 apnic wrong origin
202.71.96.0/20 /23 AS17971 apnic too specific
202.71.96.0/20 /23 AS18206 apnic wrong origin

Registry

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

Delegated block
202.71.96.0/20
RIR
APNIC
Country
🇲🇾 MY
Status
allocated
Allocated
2001-10-12

Less specific routes

Announced prefixes that contain this one

Nothing less specific is announced.

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-22 11:38:11Z origin change AS18206 → AS17971 8522914584531820617971
2026-09-22 11:29:21Z origin change AS17971 → AS18206 5572018206
2026-09-18 07:14:26Z origin change AS18206 → AS17971 57381503041299584531820617971