210.48.148.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 22 5572018206 2026-09-18 2026-09-22
AS17971 TM TECHNOLOGY SERVICES SDN. BHD. RPKI valid 19 34549584531820617971 2026-09-18 2026-09-22

RPKI

3 ROAs cover this prefix

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

Registry

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

Delegated block
210.48.144.0/20
RIR
APNIC
Country
🇲🇾 MY
Status
allocated
Allocated
2006-06-26

Less specific routes

Announced prefixes that contain this one

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-22 11:30:23Z origin change AS17971 → AS18206 5572018206
2026-09-22 10:41:47Z origin change AS18206 → AS17971 328840327727174584531820617971
2026-09-22 10:33:58Z origin change AS17971 → AS18206 8522914478818206
2026-09-22 10:25:19Z origin change AS18206 → AS17971 57821125863257584531820617971
2026-09-22 10:09:47Z origin change AS17971 → AS18206 8522914478818206
2026-09-22 09:42:21Z origin change AS18206 → AS17971 328840327727174584531820617971
2026-09-22 07:28:52Z origin change AS17971 → AS18206 8522914478818206
2026-09-22 00:05:38Z origin change AS18206 → AS17971 328840327727174584531820617971
2026-09-21 13:30:29Z origin change AS17971 → AS18206 202365506736453478818206
2026-09-18 07:14:26Z origin change AS18206 → AS17971 57381503041299584531820617971