206.127.136.0/21 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
AS33154 DQE Communications LLC no ROA 40 3454917433154 2026-09-18 2026-09-22
AS18572 Beaver Valley Intermediate Unit #27 no ROA 3 1490711164505018572 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
206.127.136.0/21
RIR
ARIN
Country
πŸ‡ΊπŸ‡Έ US
Status
allocated
Allocated
2015-06-15

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-22 11:39:29Z origin change AS33154 β†’ AS18572 85211164505018572
2026-09-22 10:41:43Z origin change AS18572 β†’ AS33154 32884032772717433154
2026-09-22 10:11:51Z origin change AS33154 β†’ AS18572 85211164505018572
2026-09-22 09:42:18Z origin change AS18572 β†’ AS33154 32884032772717433154
2026-09-22 07:30:54Z origin change AS33154 β†’ AS18572 85211164505018572