166.86.194.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 |
|---|---|---|---|---|---|
| AS213735 Rackspace Germany GmbH | no ROA | 29 | 377211323712200213735 | 2026-10-01 | 2026-10-21 |
| AS213740 Rackspace Germany GmbH | no ROA | 13 | 34549129912200213740 | 2026-09-22 | 2026-10-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
- 166.86.0.0/16
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2015-11-10
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 166.86.192.0/22 v4 | AS213740 Rackspace Germany GmbH | no ROA | 43 | 3454917412200213740 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.