31.77.188.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 |
|---|---|---|---|---|---|
| AS207957 SERV.HOST GROUP LTD | no ROA | 38 | 3772149418207957 | 2026-09-18 | 2026-09-20 |
| AS199417 Serghei Samoilov | no ROA | 4 | 5572069393920214639199417 | 2026-09-18 | 2026-09-20 |
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
- 31.76.0.0/15
- RIR
- RIPENCC
- Country
- 🇺🇸 US
- Status
- allocated
- Allocated
- 2010-11-25
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.