170.55.165.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 |
|---|---|---|---|---|---|
| AS46887 Zayo (fka. Crown Castle) | no ROA | 40 | 34549646146887 | 2026-09-18 | 2026-09-22 |
| AS33724 VOLICO | no ROA | 2 | 20409234019330333724 | 2026-09-18 | 2026-09-22 |
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
- 170.55.0.0/16
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1994-02-15
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 170.55.0.0/16 v4 | AS33132 Zayo Bandwidth | no ROA | 42 | 3454964614688733132 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.