91.217.58.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 |
|---|---|---|---|---|---|
| AS197251 FOP TERESHCHENKO OLEKSANDR TROHUMOVICH | no ROA | 34 | 24482197251 | 2026-09-18 | 2026-09-20 |
| AS6 ATOS IT Solutions and Services, Inc. | no ROA | 7 | 2265212996204505811972516 | 2026-09-18 | 2026-09-20 |
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
- 91.217.58.0/23
- RIR
- RIPENCC
- Country
- 🇺🇦 UA
- Status
- assigned
- Allocated
- 2010-08-30
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 |
|---|---|---|---|---|
| 91.217.58.0/24 v4 | AS197251 FOP TERESHCHENKO OLEKSANDR TROHUMOVICH | no ROA | 12 | 2026-09-18 |
| 91.217.59.0/24 v4 | AS197251 FOP TERESHCHENKO OLEKSANDR TROHUMOVICH | no ROA | 12 | 2026-09-18 |