216.172.136.0/24 RPKI valid 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
AS3561 Lumen (ex. Savvis) RPKI valid 40 3772133563561 2026-09-18 2026-09-22
AS18779 EGIHosting RPKI valid 3 59919900239699818779 2026-09-18 2026-09-22

RPKI

2 ROAs cover this prefix

ROA prefixMax lengthAuthorised originTrust anchorResult for this route
216.172.136.0/24 /24 AS3561 arin authorises it
216.172.128.0/19 /24 AS18779 arin wrong origin

Registry

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

Delegated block
216.172.128.0/19
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
2011-06-21

Less specific routes

Announced prefixes that contain this one

Prefix Origin RPKI Peers Sample path First seen
216.172.128.0/19 v4 AS18779 EGIHosting RPKI valid 42 34549325718779 2026-09-18

More specific routes

0 announced prefixes inside this one

Nothing more specific is announced.

Recorded changes

WhenChangeOriginPath
2026-09-22 11:29:50Z origin change AS18779 β†’ AS3561 55720693933563561
2026-09-22 10:44:15Z origin change AS3561 β†’ AS18779 5782112586325739699818779
2026-09-22 10:37:26Z origin change AS18779 β†’ AS3561 852291433563561
2026-09-22 10:25:20Z origin change AS3561 β†’ AS18779 5782112586325739699818779
2026-09-18 07:14:22Z origin change AS18779 β†’ AS3561 5738150304129933563561