199.18.71.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 |
|---|---|---|---|---|---|
| AS33167 Southwest Ohio Computer Association | no ROA | 42 | 20205618133167 | 2026-09-18 | 2026-09-26 |
| AS401724 Hamilton Connects | no ROA | 6 | 35493356401724 | 2026-09-18 | 2026-09-26 |
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
- 199.18.0.0/16
- RIR
- ARIN
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 1993-09-30
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 199.18.0.0/16 v4 | AS600 OARnet | no ROA | 48 | 37721600 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-09-24 07:40:17Z | origin change | AS401724 → AS33167 | 70186003316733167331673316733167331673316733167331673316733167 |
| 2026-09-24 07:20:35Z | origin change | AS33167 → AS401724 | 70183356401724 |
| 2026-09-21 05:12:19Z | origin change | AS401724 → AS33167 | 2023656939618133167 |
| 2026-09-21 05:03:56Z | origin change | AS33167 → AS401724 | 216285828067623356401724 |
| 2026-09-18 04:44:39Z | origin change | AS401724 → AS33167 | 388556939618133167 |
| 2026-09-18 04:38:05Z | origin change | AS401724 → AS33167 | 6939618133167 |