2801:c4:1439::/48 no ROA 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
AS272336 Secretaría de Relaciones Exteriores no ROA 32 37721676217072272336 2026-09-18 2026-09-26
AS17072 TOTAL PLAY TELECOMUNICACIONES, S.A.P.I. DE C.V. no ROA 1 1490717072 2026-09-25 2026-09-26

RPKI

No ROA covers this prefix

No ROA covers this prefix, so origin validation returns "unknown". That is not a fault; most of the table is still unsigned.

Registry

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

Delegated block
2801:c4:1000::/36
RIR
LACNIC
Country
🇲🇽 MX
Status
assigned
Allocated
2023-10-17

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-26 23:04:55Z origin change AS17072 → AS272336 34800296329002676217072272336
2026-09-26 19:00:37Z origin change AS272336 → AS17072 1490717072
2026-09-26 05:29:05Z origin change AS17072 → AS272336 612186939676217072272336
2026-09-25 15:28:27Z origin change AS272336 → AS17072 1490717072
2026-09-25 15:28:17Z origin change AS17072 → AS272336 149073356676217072272336
2026-09-25 15:18:27Z origin change AS272336 → AS17072 1490717072