bgpreport

Network · data from 2026-11-12

AS4382 Indonusa System Integrator Prima

Registry name: INDONUSA-ID - PT. Indonusa System Integrator Prima, ID · PeeringDB

9IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 33.3% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
11Route objects not announced registered with origin AS4382, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS4382, 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.
2403:b900:151f::/48 Valid Nonecovered by 2403:b900::/32 634 100% 71
2403:b900:2020::/48 Valid Nonecovered by 2403:b900::/32 634 100% 71
202.93.129.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.130.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.131.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.133.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.139.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.140.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.141.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.142.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
202.93.143.0/24 Valid Other IRR onlyNTTCOM 673 100% 69
2403:b900::/32 Valid Other IRR onlyRADB 34 5%low visibility 29

AS-SET

AS4382'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 23 are in fix.csv.

  • Route object: none2
  • Route object: RIR10
  • Route object: not announced11
ChangePrefix or setDetailFull-table peers
Route object: none2403:b900:151f::/48No route object for it. A route object for 2403:b900::/32 with origin AS4382 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4382 in the RIR database for the space.634 of 636
Route object: none2403:b900:2020::/48No route object for it. A route object for 2403:b900::/32 with origin AS4382 covers it (filters allowing more-specifics accept it). Add a route object with origin AS4382 in the RIR database for the space.634 of 636
Route object: RIR202.93.129.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.130.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.131.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.133.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.139.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.140.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.141.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.142.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR202.93.143.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
Route object: RIR2403:b900::/32Route object only in RADB. Add it in the RIR database for the space.34 of 636

Route objects not announced

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

202.93.128.0/20APNIC, RADBNo ROA
202.93.128.0/21NTTCOM, RADBNo ROA
202.93.128.0/22NTTCOMNo ROA
202.93.128.0/23NTTCOMNo ROA
202.93.128.0/24NTTCOMValid
202.93.132.0/24NTTCOMValid
202.93.134.0/24NTTCOMValid
202.93.135.0/24NTTCOMValid
202.93.136.0/24NTTCOMValid
202.93.137.0/24NTTCOMValid
202.93.138.0/24NTTCOMValid

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.