2804:6cac:ff00::/40 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
AS266414 EXPRESS NETWORK-ME no ROA 34 37721676252468266414 2026-09-18 2026-09-19
AS270484 NOVA NETWORK TELECOM LTDA no ROA 1 24482266414270484 2026-09-18 2026-09-19

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
2804:6cac::/32
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2020-03-11

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2804:6cac:c000::/34 v6 AS270484 NOVA NETWORK TELECOM LTDA no ROA 2 24482270484 2026-09-18
2804:6cac:8000::/33 v6 AS270484 NOVA NETWORK TELECOM LTDA no ROA 2 24482270484 2026-09-18
2804:6cac::/32 v6 AS270484 NOVA NETWORK TELECOM LTDA no ROA 34 37721270484 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-18 04:46:23Z origin change AS270484 → AS266414 348002963290023746852468266414
2026-09-18 04:05:49Z origin change AS270484 → AS266414 34800296329002335652468266414