185.167.176.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 |
|---|---|---|---|---|---|
| AS207021 ipcom GmbH | no ROA | 36 | 3454936236207021 | 2026-09-18 | 2026-09-21 |
| AS1921 ipcom GmbH | no ROA | 7 | 3800188491921 | 2026-09-18 | 2026-09-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
- 185.167.176.0/22
- RIR
- RIPENCC
- Country
- 🇸🇪 SE
- Status
- allocated
- Allocated
- 2016-09-13
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.