88.218.30.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 |
|---|---|---|---|---|---|
| AS211895 Serverius Holding B.V. | no ROA | 42 | 3772150673211895 | 2026-10-20 | 2026-10-22 |
| AS50673 Serverius Holding B.V. | no ROA | 1 | 443935805750673 | 2026-10-20 | 2026-10-22 |
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
- 88.218.28.0/22
- RIR
- RIPENCC
- Country
- 🇺🇦 UA
- Status
- allocated
- Allocated
- 2018-12-14
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.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-10-20 17:13:45Z | origin change | AS50673 → AS211895 | 32884032772717450673211895 |
| 2026-10-20 17:11:37Z | origin change | AS211895 → AS50673 | 443935805750673 |
| 2026-10-20 12:43:16Z | origin change | AS50673 → AS211895 | 2040922076650673211895 |
| 2026-10-20 12:43:16Z | origin change | AS211895 → AS50673 | 443935805750673 |
| 2026-10-20 12:43:16Z | origin change | AS50673 → AS211895 | 494324836250673211895 |
| 2026-10-20 12:40:29Z | new prefix | AS50673 Serverius Holding B.V. | 20236550673 |