5.181.61.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 |
|---|---|---|---|---|---|
| AS47764 LLC VK (Mail.ru) | RPKI valid | 41 | 3772147764 | 2026-09-18 | 2026-09-27 |
| AS28709 LLC VK | RPKI invalid | 1 | 4967328709 | 2026-09-18 | 2026-09-27 |
RPKI
1 ROA covers this prefix
| ROA prefix | Max length | Authorised origin | Trust anchor | Result for this route |
|---|---|---|---|---|
| 5.181.61.0/24 | /24 | AS47764 | ripe | authorises it |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 5.181.60.0/22
- RIR
- RIPENCC
- Country
- 🇷🇺 RU
- Status
- allocated
- Allocated
- 2019-04-02
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 5.181.60.0/22 v4 | AS47764 LLC VK (Mail.ru) | no ROA | 43 | 3772147764 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.