65.167.208.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 |
|---|---|---|---|---|---|
| AS174 Cogent Communications, LLC | no ROA | 36 | 34549174 | 2026-09-18 | 2026-09-27 |
| AS32091 Verizon Business | no ROA | 3 | 354933561207932091 | 2026-09-18 | 2026-09-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
- 65.160.0.0/13
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2000-09-19
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 65.160.0.0/13 v4 | AS174 Cogent Communications, LLC | no ROA | 40 | 34549174 | 2026-09-18 |
More specific routes
2 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 65.167.208.0/24 v4 | AS174 Cogent Communications, LLC | no ROA | 40 | 2026-09-18 |
| 65.167.209.0/24 v4 | AS174 Cogent Communications, LLC | no ROA | 40 | 2026-09-18 |