103.36.135.0/24 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 |
|---|---|---|---|---|
| 103.36.135.0/24 | /24 | AS55994 | apnic | authorises it |
| 103.36.135.0/24 | /24 | AS138421 | apnic | wrong origin |
| 103.36.134.0/23 | /23 | AS4811 | apnic | wrong origin |
| 103.36.132.0/22 | /22 | AS4812 | apnic | wrong origin |
| 103.36.132.0/22 | /22 | AS55994 | apnic | too specific |
Registry
Who this address space is delegated to, regardless of whether it is routed
- Delegated block
- 103.36.132.0/22
- RIR
- APNIC
- Country
- 🇨🇳 CN
- Status
- allocated
- Allocated
- 2014-08-15
Less specific routes
Announced prefixes that contain this one
| Prefix | Origin | RPKI | Peers | Sample path | First seen |
|---|---|---|---|---|---|
| 103.36.134.0/23 v4 | AS4811 China Telecom Shanghai IDC Network | RPKI valid | 42 | 701841344811 | 2026-09-18 |
| 103.36.132.0/22 v4 | AS4812 China Telecom Shanghai Province Network | RPKI valid | 41 | 701841344812 | 2026-09-18 |
More specific routes
0 announced prefixes inside this one
Nothing more specific is announced.
Recorded changes
| When | Change | Origin | Path |
|---|---|---|---|
| 2026-10-14 18:06:19Z | origin change | AS138421 → AS55994 | 55720174765845398082440055994 |
| 2026-10-14 03:32:12Z | origin change | AS55994 → AS138421 | 3798956300132132100994837138421 |
| 2026-10-12 10:54:34Z | origin change | AS138421 → AS55994 | 2040922076629169352808966158025845398082440055994 |
| 2026-10-07 16:09:07Z | origin change | AS55994 → AS138421 | 3798956300132132100994837138421 |