185.217.136.0/24 RPKI valid 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 |
|---|---|---|---|---|---|
| AS200313 IT WEB LTD | RPKI valid | 46 | 3772157043200313 | 2026-09-18 | 2026-09-26 |
| AS57043 HOSTKEY B.V. | RPKI invalid | 1 | 49673321657043 | 2026-09-18 | 2026-09-26 |
RPKI
1 ROA covers this prefix
| ROA prefix | Max length | Authorised origin | Trust anchor | Result for this route |
|---|---|---|---|---|
| 185.217.136.0/24 | /24 | AS200313 | ripe | authorises it |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 185.217.136.0/22
- RIR
- RIPENCC
- Country
- 🇻🇬 VG
- Status
- allocated
- Allocated
- 2017-08-15
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.