43.226.128.0/23 RPKI valid 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
RPKI
5 ROAs cover this prefix
| ROA prefix | Max length | Authorised origin | Trust anchor | Result for this route |
|---|---|---|---|---|
| 43.226.128.0/20 | /24 | AS4837 | apnic | authorises it |
| 43.226.128.0/20 | /24 | AS23650 | apnic | wrong origin |
| 43.226.128.0/20 | /24 | AS56046 | apnic | wrong origin |
| 43.226.128.0/20 | /24 | AS131483 | apnic | wrong origin |
| 43.226.128.0/20 | /24 | AS151300 | apnic | wrong origin |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 43.226.128.0/22
- RIR
- APNIC
- Country
- 🇨🇳 CN
- Status
- allocated
- Allocated
- 2014-12-15
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 43.226.128.0/20 v4 | AS23650 China Telecom Jiangsu Province IDC Network | RPKI valid | 41 | 7018413423650 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.