205.172.80.0/20 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 |
|---|---|---|---|---|---|
| AS18756 Level 3 Parent, LLC | no ROA | 24 | 14907335618756 | 2026-09-18 | 2026-09-21 |
| AS10753 Level 3 Parent, LLC | no ROA | 19 | 37721335610753 | 2026-09-18 | 2026-09-21 |
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
- 205.172.80.0/20
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1995-03-31
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-09-19 21:35:10Z | origin change | AS18756 → AS10753 | 345492914335610753 |
| 2026-09-19 21:33:02Z | origin change | AS10753 → AS18756 | 345492914335618756 |
| 2026-09-19 08:44:00Z | origin change | AS18756 → AS10753 | 328840327727174335610753 |
| 2026-09-19 08:30:27Z | origin change | AS10753 → AS18756 | 2950415935174335618756 |
| 2026-09-18 20:59:20Z | origin change | AS18756 → AS10753 | 328840327727174335610753 |
| 2026-09-18 20:29:17Z | origin change | AS10753 → AS18756 | 496733216335618756 |
| 2026-09-18 14:03:03Z | origin change | AS18756 → AS10753 | 328840327727174335610753 |