2804:854:b::/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
AS28368 Wirelink (Sobralnet) no ROA 18 2448228368 2026-09-18 2026-09-18
AS61832 Giga+ Empresas no ROA 15 70181295661832 2026-09-18 2026-09-18

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:854::/32
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2012-01-26

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
2804:854::/32 v6 AS28368 Wirelink (Sobralnet) no ROA 35 244826183228368 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-19 02:26:06Z origin change AS28368 → AS61832 494324836290021295661832
2026-09-19 02:25:22Z origin change AS61832 → AS28368 4943221551031543693928368
2026-09-18 09:01:56Z origin change AS28368 → AS61832 580571741295661832
2026-09-18 07:11:01Z origin change AS61832 → AS28368 57381693928368
2026-09-18 06:41:36Z origin change AS28368 → AS61832 494324836290021295661832
2026-09-18 06:41:25Z origin change AS61832 → AS28368 4943221551031543693928368