133.88.76.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 |
|---|---|---|---|---|---|
| AS131950 EnjoyVC Japan Corporation | no ROA | 31 | 345492914139076131950 | 2026-09-18 | 2026-09-26 |
| AS139076 EnjoyVC Japan Corporation | no ROA | 10 | 38001139076 | 2026-09-18 | 2026-09-26 |
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
- 133.0.0.0/8
- RIR
- APNIC
- Country
- 🇯🇵 JP
- Status
- allocated
- Allocated
- 1997-03-01
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.