2804:91c8:4000::/36 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
AS274664 UBBY INTERNET LTDA no ROA 34 2448253102274664 2026-09-18 2026-09-22
AS270844 AXION3 TELECOM LTDA no ROA 1 2162858280676252468274664270844 2026-09-18 2026-09-22

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:91c8::/32
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2024-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-21 17:28:53Z origin change AS270844 → AS274664 34549645326862453102274664
2026-09-21 13:29:16Z origin change AS274664 → AS270844 216285828067625246852468524685246852468524685246852468524685246852468274664270844270844270844
2026-09-21 11:10:21Z origin change AS270844 → AS274664 5030029141295626862453102274664
2026-09-21 05:08:24Z origin change AS274664 → AS270844 216285828067625246852468524685246852468524685246852468524685246852468274664270844270844270844