176.59.122.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 |
|---|---|---|---|---|---|
| AS48092 T2 Mobile LLC Nizhniy Novgorod branch | no ROA | 37 | 3454920764480923937448092 | 2026-09-18 | 2026-10-24 |
| AS39374 T2 Mobile LLC | no ROA | 8 | 377214809239374 | 2026-09-18 | 2026-10-24 |
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
- 176.59.0.0/16
- RIR
- RIPENCC
- Country
- 🇷🇺 RU
- Status
- allocated
- Allocated
- 2011-06-06
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 176.59.96.0/19 v4 | AS48092 T2 Mobile LLC Nizhniy Novgorod branch | no ROA | 45 | 3772148092 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.