125.0.147.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 |
|---|---|---|---|---|---|
| AS55374 FUJITSU LIMITED | no ROA | 22 | 38001251655374 | 2026-09-18 | 2026-09-22 |
| AS55386 FUJITSU LIMITED | no ROA | 19 | 3454929144713251055386 | 2026-09-18 | 2026-09-22 |
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
- 125.0.128.0/17
- RIR
- APNIC
- Country
- 🇯🇵 JP
- Status
- allocated
- Allocated
- 2005-07-14
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 125.0.128.0/17 v4 | AS2510 FUJITSU LIMITED | no ROA | 42 | 34549291447132510 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.