202.75.60.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
AS18206 TM TECHNOLOGY SERVICES SDN. BHD. RPKI valid 38 34549875718206 2026-09-18 2026-09-28
AS17971 TM TECHNOLOGY SERVICES SDN. BHD. RPKI valid 3 3800147881820617971 2026-09-18 2026-09-28

RPKI

2 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
202.75.48.0/20 /24 AS17971 apnic wrong origin
202.75.48.0/20 /24 AS18206 apnic authorises it

Registry

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

Delegated block
202.75.48.0/20
RIR
APNIC
Country
🇲🇾 MY
Status
allocated
Allocated
2004-07-21

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
202.75.60.0/23 v4 AS17971 TM TECHNOLOGY SERVICES SDN. BHD. RPKI valid 9 3800147881820617971 2026-09-18
202.75.60.0/23 v4 AS18206 TM TECHNOLOGY SERVICES SDN. BHD. RPKI valid 32 5572018206 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-23 10:43:21Z origin change AS17971 → AS18206 481852914875718206
2026-09-23 10:35:29Z origin change AS18206 → AS17971 4818547881820617971
2026-09-21 22:43:19Z origin change AS17971 → AS18206 59919900212956875718206
2026-09-21 09:21:47Z origin change AS18206 → AS17971 46081221463747881820617971
2026-09-21 09:17:37Z origin change AS17971 → AS18206 460875751299875718206
2026-09-21 08:52:06Z origin change AS18206 → AS17971 46081221463747881820617971