178.34.77.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 |
|---|---|---|---|---|---|
| AS201851 PJSC "PIK SPECIALIZED DEVELOPER" | RPKI valid | 41 | 2448212389201851 | 2026-09-24 | 2026-10-10 |
| AS51668 PIK SHb PJSC | RPKI invalid | 1 | 496731238951668 | 2026-09-18 | 2026-10-10 |
RPKI
3 ROAs cover this prefix
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 178.34.0.0/17
- RIR
- RIPENCC
- Country
- 🇷🇺 RU
- Status
- allocated
- Allocated
- 2010-01-21
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 178.34.64.0/19 v4 | AS12389 Rostelecom PJSC | RPKI valid | 45 | 2448212389 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-10-02 23:51:59Z | origin change | AS51668 → AS201851 | 48185335612389201851 |
| 2026-10-02 22:59:59Z | origin change | AS201851 → AS51668 | 496731238951668 |
| 2026-10-02 22:59:09Z | origin change | AS51668 → AS201851 | 4967312389201851 |
| 2026-10-02 22:58:57Z | origin change | AS201851 → AS51668 | 496731238951668 |