217.198.14.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 |
|---|---|---|---|---|---|
| AS216322 Atomdata-Innopolis JSC | no ROA | 27 | 3772131133216322 | 2026-09-18 | 2026-10-17 |
| AS201757 Joint-Stock Commercial Bank Ak Bars (OJSC) | no ROA | 17 | 22652693912389201757 | 2026-09-18 | 2026-10-17 |
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
- 217.198.0.0/20
- RIR
- RIPENCC
- Country
- 🇷🇺 RU
- Status
- allocated
- Allocated
- 2001-05-03
Less specific routes
Announced prefixes that contain this one
Nothing less specific is announced.
More specific routes
2 announced prefixes inside this one
| Prefix | Origin | RPKI | Peers | First seen |
|---|---|---|---|---|
| 217.198.14.0/24 v4 | AS201757 Joint-Stock Commercial Bank Ak Bars (OJSC) | no ROA | 44 | 2026-09-18 |
| 217.198.15.0/24 v4 | AS201757 Joint-Stock Commercial Bank Ak Bars (OJSC) | no ROA | 44 | 2026-09-18 |