206.187.220.0/23 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 AS | RPKI | Peers seeing it | Sample path | First seen | Last seen |
|---|---|---|---|---|---|
| AS137899 I LAYER LIMITED | no ROA | 23 | 34549291440779137899 | 2026-10-16 | 2026-10-27 |
| AS401696 cognetcloud INC | no ROA | 19 | 2448240779401696 | 2026-09-27 | 2026-10-27 |
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.187.192.0/19
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2026-09-18
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.