Network · data from 2026-11-12
AS58983 ACODA Networks Sdn Bhd
Registry name: ANSB-MY - ACODA Networks Sdn Bhd, MY · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58983, 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.
| 103.176.72.0/24 | No ROA | RIR databaseAPNIC | 673 100% |
| 45.119.160.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 45.119.162.0/23 | Valid | RIR databaseAPNIC | 673 100% |
| 103.240.176.0/22 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.240.176.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.240.176.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.240.177.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.240.178.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.240.178.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.240.179.0/24 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 2400:5880::/33 | Valid | RIR databaseAPNIC, RADB | 636 100% |
| 2400:5880:8000::/33 | Valid | RIR databaseAPNIC, RADB | 636 100% |
AS-SET
AS58983'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 7 are in fix.csv.
- ROA: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 103.176.72.0/24 | No ROA covers it. Add a ROA for AS58983, maxLength 24. |
Route objects not announced
Route objects with origin AS58983 whose prefix no peer sees AS58983 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.119.160.0/22 | APNIC | Valid |
| 45.119.160.0/24 | APNIC | Valid |
| 45.119.161.0/24 | APNIC | Valid |
| 45.119.162.0/24 | APNIC | Valid |
| 45.119.163.0/24 | APNIC | Valid |
| 2400:5880::/32 | APNIC, RADB | Valid |
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.