bgpreport

Network · data from 2026-11-12

AS140389 Dewa Bisnis Digital

Registry name: IDNIC-DBIZ-AS-ID - PT Dewa Bisnis Digital, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS140389, 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.153.2.0/23 Valid None 672 100% 67
103.253.244.0/23 Valid None 672 100% 67
103.122.2.0/24 Valid Nonecovered by 103.122.2.0/23 671 100% 67
103.122.3.0/24 Valid Nonecovered by 103.122.2.0/23 668 99% 66
103.160.213.0/24 Valid Nonecovered by 103.160.212.0/23 668 99% 67
103.179.86.0/24 Valid Nonecovered by 103.179.86.0/23 668 99% 67
103.179.87.0/24 Valid Nonecovered by 103.179.86.0/23 668 99% 67
2001:df3:5b80::/48 Valid None 636 100% 67
103.147.32.0/23 Valid Other IRR onlyRADB 673 100% 68
103.160.212.0/23 Valid Other IRR onlyRADB 673 100% 68
103.179.86.0/23 Valid Other IRR onlyRADB 673 100% 68
103.147.32.0/24 Valid Other IRR onlyRADB 672 100% 68
103.147.33.0/24 Valid Other IRR onlyRADB 672 100% 68
103.150.61.0/24 Valid Other IRR onlyRADB 672 100% 68
103.253.245.0/24 Valid Other IRR onlyRADB 672 100% 68
103.150.60.0/24 Valid Other IRR onlyRADB 669 99% 68
103.153.2.0/24 Valid Other IRR onlyRADB 668 99% 67
103.153.3.0/24 Valid Other IRR onlyRADB 668 99% 67
103.160.212.0/24 Valid Other IRR onlyRADB 668 99% 67
103.253.244.0/24 Valid Other IRR onlyRADB 668 99% 67
103.122.2.0/23 Valid RIR databaseAPNIC 673 100% 68
103.150.60.0/23 Valid RIR databaseAPNIC 673 100% 68

AS-SET

AS140389'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 20 are in fix.csv.

  • Route object: none8
  • Route object: RIR12
ChangePrefix or setDetailFull-table peers
Route object: none103.153.2.0/23No route object for it. Add a route object with origin AS140389 in the RIR database for the space.672 of 673
Route object: none103.253.244.0/23No route object for it. Add a route object with origin AS140389 in the RIR database for the space.672 of 673
Route object: none103.122.2.0/24No route object for it. A route object for 103.122.2.0/23 with origin AS140389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140389 in the RIR database for the space.671 of 673
Route object: none103.122.3.0/24No route object for it. A route object for 103.122.2.0/23 with origin AS140389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140389 in the RIR database for the space.668 of 673
Route object: none103.160.213.0/24No route object for it. A route object for 103.160.212.0/23 with origin AS140389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140389 in the RIR database for the space.668 of 673
Route object: none103.179.86.0/24No route object for it. A route object for 103.179.86.0/23 with origin AS140389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140389 in the RIR database for the space.668 of 673
Route object: none103.179.87.0/24No route object for it. A route object for 103.179.86.0/23 with origin AS140389 covers it (filters allowing more-specifics accept it). Add a route object with origin AS140389 in the RIR database for the space.668 of 673
Route object: none2001:df3:5b80::/48No route object for it. Add a route object with origin AS140389 in the RIR database for the space.636 of 636
Route object: RIR103.147.32.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.160.212.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.179.86.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.147.32.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.147.33.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.150.61.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.253.245.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.150.60.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR103.153.2.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR103.153.3.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR103.160.212.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR103.253.244.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

Every route object with origin AS140389 is announced.

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.