bgpreport

Network · data from 2026-11-12

AS45144 Net Onboard Sdn Bhd

Registry name: NETONBOARD-MY - Net Onboard Sdn Bhd - Quality & Reliable Cloud Hosting Provider, MY · PeeringDB

19IPv4 routes 94.7% RPKI valid · 94.7% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS45144, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45144, 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.4.7.0/24 No ROA Other origin only 672 100% 67
43.252.36.0/24 Valid RIR databaseAPNIC, RADB, REACH 673 100% 66
43.252.37.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
43.252.38.0/24 Valid RIR databaseAPNIC 673 100% 66
103.78.47.0/24 Valid RIR databaseAPNIC, RADB 673 100% 66
182.239.40.0/22 Valid RIR databaseAPNIC, RADB 673 100% 66
182.239.40.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 66
182.239.41.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 66
182.239.42.0/24 Valid RIR databaseAPNIC, RADB, REACH 673 100% 66
182.239.43.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB, REACH 673 100% 66
103.4.6.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.211.239.0/24 Valid RIR databaseAPNIC 672 100% 66
220.158.208.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
220.158.209.0/24 Valid RIR databaseAPNIC, RADB 672 100% 66
103.78.48.0/23 Valid RIR databaseAPNIC, RADB 671 100% 66
103.78.48.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.78.49.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.4.4.0/24 Valid RIR databaseAPNIC, RADB 670 100% 68
103.4.5.0/24 Valid RIR databaseAPNIC, RADB 670 100% 68

AS-SET

AS45144'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 14 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none103.4.7.0/24No ROA covers it. Add a ROA for AS45144, maxLength 24.672 of 673
Route object: none103.4.7.0/24Route objects for it name AS45352. Add a route object with origin AS45144 in the RIR database for the space.672 of 673

Route objects not announced

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

43.252.36.0/22APNICValid
43.252.36.0/23APNICValid
43.252.38.0/23APNICValid
43.252.39.0/24APNICValid
103.4.4.0/23APNICValid
182.239.40.0/23APNIC, NTTCOM, RADBValid
182.239.42.0/23APNIC, RADBValid
220.158.208.0/22APNICValid
220.158.208.0/23APNICValid
220.158.210.0/23APNICValid
220.158.210.0/24APNICValid
220.158.211.0/24APNICValid

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.