192.170.158.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 |
|---|---|---|---|---|---|
| AS32475 Internap Holding LLC | no ROA | 23 | 5805717432475 | 2026-09-18 | 2026-09-24 |
| AS14636 Internap Holding LLC | no ROA | 20 | 3454918282424714636 | 2026-09-18 | 2026-09-24 |
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
- 192.170.152.0/21
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2012-11-07
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
4 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 192.170.158.0/24 v4 | AS14636 Internap Holding LLC | no ROA | 20 | 2026-09-18 |
| 192.170.158.0/24 v4 | AS32475 Internap Holding LLC | no ROA | 23 | 2026-09-18 |
| 192.170.159.0/24 v4 | AS14636 Internap Holding LLC | no ROA | 19 | 2026-09-18 |
| 192.170.159.0/24 v4 | AS32475 Internap Holding LLC | no ROA | 24 | 2026-09-18 |