Network · data from 2026-11-12

AS58910 ACODA

Registry name: ASSB-AS-MY - ACODA Networks Sdn Bhd, MY · PeeringDB

13IPv4 routes 100.0% RPKI valid · 100.0% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

3Route objects not announced registered with origin AS58910, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS58910, 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.


43.241.96.0/22	Valid	Other IRR onlyRADB	673 100%	66
103.18.88.0/22	Valid	Other IRR onlyRADB	673 100%	66
103.18.88.0/23	Valid	Other IRR onlyRADB	673 100%	66
103.18.90.0/23	Valid	Other IRR onlyRADB	673 100%	66
43.241.96.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
43.241.97.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
43.241.98.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
43.241.99.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
103.18.88.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
103.18.89.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	68
103.18.90.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
103.18.91.0/24	Valid	RIR databaseAPNIC, RADB	673 100%	66
103.145.156.0/24	Valid	RIR databaseAPNIC	673 100%	68
2400:5380::/33	Valid	RIR databaseAPNIC, RADB	636 100%	69
2400:5380:8000::/33	Valid	RIR databaseAPNIC, RADB	636 100%	69

AS-SET

AS58910'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.

Route object: RIR4
Route object: not announced3

Change	Prefix or set	Detail	Full-table peers
Route object: RIR	43.241.96.0/22	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.18.88.0/22	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.18.88.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673
Route object: RIR	103.18.90.0/23	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

Route object: RIR

43.241.96.0/22

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

103.18.88.0/22

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

103.18.88.0/23

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route object: RIR

103.18.90.0/23

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

Route objects with origin AS58910 whose prefix no peer sees AS58910 announce. Many are kept on purpose (backup routes, space announced only in some places).


43.241.96.0/23	RADB	Valid
43.241.98.0/23	RADB	Valid
2400:5380::/32	APNIC, RADB	Valid

43.241.96.0/23

RADB

Valid

43.241.98.0/23

RADB

Valid

2400:5380::/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.