Network · data from 2026-11-12
AS24321 OCESB
Registry name: OCENET-AS-AP - OCE Sdn Bhd ISP, MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS24321, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 153.76.232.0/22 | No ROA | None | 670 100% |
| 161.248.9.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 202.87.216.0/22 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
| 153.76.236.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 202.73.8.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 672 100% |
AS-SET
AS24321's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 83 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: RIR1
- Route object: not announced79
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 153.76.232.0/22 | No ROA covers it. Add a ROA for AS24321, maxLength 22. |
| Route object: none | 153.76.232.0/22 | No route object for it. Add a route object with origin AS24321 in the RIR database for the space. |
| ROA: none | 161.248.9.0/24 | No ROA covers it. Add a ROA for AS24321, maxLength 24. |
| Route object: RIR | 161.248.9.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS24321 whose prefix no peer sees AS24321 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 61.4.96.0/19 | RADB | No ROA |
| 61.4.96.0/20 | NTTCOM, RADB, RIPE-NONAUTH | No ROA |
| 61.4.96.0/21 | NTTCOM, RADB | No ROA |
| 61.4.96.0/22 | NTTCOM, RADB | No ROA |
| 61.4.96.0/23 | NTTCOM, RADB | No ROA |
| 61.4.98.0/23 | NTTCOM, RADB | No ROA |
| 61.4.104.0/21 | NTTCOM, RADB | No ROA |
| 61.4.108.0/22 | NTTCOM, RADB | No ROA |
| 61.4.108.0/23 | NTTCOM, RADB | No ROA |
| 61.4.110.0/23 | NTTCOM, RADB | No ROA |
| 61.4.114.0/23 | RADB | No ROA |
| 61.4.118.0/23 | RADB | No ROA |
| 61.4.120.0/22 | NTTCOM | No ROA |
| 61.4.120.0/23 | NTTCOM, RADB | No ROA |
| 61.4.122.0/23 | NTTCOM, RADB | No ROA |
| 61.4.126.0/23 | RADB | No ROA |
| 118.107.192.0/18 | NTTCOM, RADB | No ROA |
| 118.107.192.0/19 | NTTCOM, RADB, RIPE-NONAUTH | No ROA |
| 118.107.192.0/20 | NTTCOM, RADB | No ROA |
| 118.107.192.0/22 | RADB | No ROA |
| 118.107.192.0/23 | RADB | No ROA |
| 118.107.194.0/23 | RADB | No ROA |
| 118.107.196.0/22 | RADB | No ROA |
| 118.107.196.0/23 | RADB | No ROA |
| 118.107.196.0/24 | RADB | No ROA |
| 118.107.197.0/24 | RADB | No ROA |
| 118.107.198.0/23 | RADB | No ROA |
| 118.107.198.0/24 | RADB | No ROA |
| 118.107.199.0/24 | RADB | No ROA |
| 118.107.208.0/20 | NTTCOM, RADB | No ROA |
| 118.107.208.0/23 | RADB | No ROA |
| 118.107.210.0/23 | RADB | No ROA |
| 118.107.212.0/22 | RADB | No ROA |
| 118.107.212.0/23 | RADB | No ROA |
| 118.107.214.0/23 | RADB | No ROA |
| 118.107.216.0/21 | NTTCOM, RADB | No ROA |
| 118.107.216.0/22 | NTTCOM | No ROA |
| 118.107.216.0/23 | NTTCOM, RADB | No ROA |
| 118.107.218.0/23 | NTTCOM, RADB | No ROA |
| 118.107.220.0/22 | NTTCOM | No ROA |
| 118.107.220.0/23 | NTTCOM, RADB | No ROA |
| 118.107.222.0/23 | NTTCOM, RADB | No ROA |
| 118.107.224.0/19 | NTTCOM | No ROA |
| 118.107.224.0/20 | NTTCOM | No ROA |
| 118.107.224.0/21 | NTTCOM | No ROA |
| 118.107.224.0/22 | NTTCOM, RADB | No ROA |
| 118.107.224.0/23 | NTTCOM, RADB | No ROA |
| 118.107.226.0/23 | NTTCOM, RADB | No ROA |
| 118.107.230.0/23 | RADB | No ROA |
| 118.107.232.0/21 | NTTCOM | No ROA |
| 118.107.236.0/22 | NTTCOM, RADB | No ROA |
| 118.107.236.0/23 | NTTCOM, RADB | No ROA |
| 118.107.238.0/23 | NTTCOM, RADB | No ROA |
| 118.107.240.0/20 | NTTCOM | No ROA |
| 118.107.240.0/21 | NTTCOM | No ROA |
| 118.107.240.0/22 | NTTCOM, RADB | No ROA |
| 118.107.240.0/23 | NTTCOM, RADB | No ROA |
| 118.107.242.0/23 | NTTCOM, RADB | No ROA |
| 118.107.244.0/22 | NTTCOM, RADB | No ROA |
| 118.107.244.0/23 | NTTCOM, RADB | No ROA |
| 118.107.246.0/23 | NTTCOM, RADB | No ROA |
| 118.107.248.0/21 | NTTCOM | No ROA |
| 118.107.248.0/22 | NTTCOM, RADB | No ROA |
| 118.107.248.0/23 | NTTCOM, RADB | No ROA |
| 118.107.250.0/23 | NTTCOM, RADB | No ROA |
| 118.107.252.0/22 | NTTCOM, RADB | No ROA |
| 118.107.252.0/23 | NTTCOM, RADB | No ROA |
| 118.107.254.0/23 | NTTCOM, RADB | No ROA |
| 202.73.8.0/21 | NTTCOM | No ROA |
| 202.73.12.0/22 | NTTCOM | No ROA |
| 202.73.12.0/23 | NTTCOM, RADB | No ROA |
| 202.73.14.0/23 | NTTCOM, RADB | No ROA |
| 202.87.216.0/21 | NTTCOM, RADB, RIPE-NONAUTH | No ROA |
| 202.87.220.0/22 | RADB | No ROA |
| 202.87.220.0/23 | RADB | No ROA |
| 202.87.222.0/23 | RADB | No ROA |
| 202.171.40.0/21 | RADB | No ROA |
| 202.171.40.0/24 | RADB | No ROA |
| 202.171.44.0/24 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.