45.230.77.0/24 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
AS267159 LTNET Telecomunicacoes EIRELE ME no ROA 42 557206939262557267159 2026-10-14 2026-10-21
AS652002 no ROA 1 21324190023356263009262557267159652002 2026-09-18 2026-10-21

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
45.230.76.0/22
RIR
LACNIC
Country
🇧🇷 BR
Status
allocated
Allocated
2018-01-22

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
45.230.76.0/23 v4 AS267159 LTNET Telecomunicacoes EIRELE ME no ROA 43 557206939262557267159 2026-09-18
45.230.76.0/22 v4 AS267159 LTNET Telecomunicacoes EIRELE ME no ROA 45 24482262296267159 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-10-13 20:57:18Z origin change AS652002 → AS267159 2040921989781743356263009262557262557267159
2026-10-13 20:57:16Z origin change AS267159 → AS652002 4608122146373356263009262557262557267159652002
2026-10-13 20:57:06Z origin change AS652002 → AS267159 176396939262557267159