199.102.216.0/22 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 |
|---|---|---|---|---|---|
| AS402506 Zenixcloud Inc | no ROA | 41 | 17639402506 | 2026-09-18 | 2026-09-20 |
| AS8796 FASTNET DATA INC | no ROA | 1 | 4439335710100998796 | 2026-09-18 | 2026-09-20 |
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
- 199.102.216.0/22
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2026-07-01
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
1 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 199.102.219.0/24 v4 | AS402506 Zenixcloud Inc | no ROA | 42 | 2026-09-18 |