209.164.208.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 AS | RPKI | Peers seeing it | Sample path | First seen | Last seen |
|---|---|---|---|---|---|
| AS15048 MetLife | no ROA | 43 | 3278715048 | 2026-10-16 | 2026-10-16 |
| AS203 Level 3 Parent, LLC | no ROA | 1 | 21324190023356203 | 2026-09-18 | 2026-10-16 |
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
- 209.164.192.0/19
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2006-04-07
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
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-10-16 00:04:57Z | origin change | AS15048 → AS203 | 1490712993356203 |
| 2026-10-16 00:04:57Z | origin change | AS203 → AS15048 | 206499345492914335615048 |
| 2026-10-16 00:04:43Z | origin change | AS203 → AS15048 | 149071299335615048 |
| 2026-10-16 00:04:42Z | origin change | AS15048 → AS203 | 349275665512993356203 |
| 2026-10-16 00:04:42Z | origin change | AS203 → AS15048 | 13830971335615048 |
| 2026-10-16 00:04:35Z | origin change | AS15048 → AS203 | 4818512993356203 |
| 2026-10-16 00:04:34Z | origin change | AS203 → AS15048 | 8523257335615048 |