103.135.3.0/24 RPKI invalid 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 |
|---|---|---|---|---|---|
| AS38320 PT Maxindo Mitra Solusi | RPKI invalid | 6 | 38001771338320 | 2026-09-19 | 2026-09-20 |
| AS138827 PT Maxindo Mitra Solusi | RPKI valid | 1 | 3492717423947138827 | 2026-09-18 | 2026-09-20 |
RPKI
1 ROA covers this prefix
| ROA prefix | Max length | Authorised origin | Trust anchor | Result for this route |
|---|---|---|---|---|
| 103.135.3.0/24 | /24 | AS138827 | apnic | wrong origin |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 103.135.0.0/22
- RIR
- APNIC
- Country
- 🇮🇩 ID
- Status
- assigned
- Allocated
- 2019-02-19
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 103.135.0.0/22 v4 | AS38320 PT Maxindo Mitra Solusi | no ROA | 41 | 34549771338320 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.