bgpreport

Network · data from 2026-11-12

AS139390 PT. Langit Mandiri Sukses

Registry name: LAMS-AS-ID - PT Langit Mandiri Sukses, ID · PeeringDB

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

Announced routes

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

38.172.152.0/24 No ROA Nonecovered by 38.172.152.0/23 3 0%low visibility 3
103.143.62.0/24 No ROA Other IRR onlyRADB 672 100% 69
103.143.63.0/24 No ROA Other IRR onlyRADB 672 100% 67
204.157.164.0/24 No ROA Other IRR onlyRADB 672 100% 67
204.157.165.0/24 No ROA Other IRR onlyRADB 672 100% 67
38.56.80.0/24 No ROA Other IRR onlyRADB 669 99% 68

AS-SET

AS139390'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 15 are in fix.csv.

  • ROA: none6
  • Route object: none1
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none38.172.152.0/24No ROA covers it. Add a ROA for AS139390, maxLength 24.3 of 673
Route object: none38.172.152.0/24No route object for it. A route object for 38.172.152.0/23 with origin AS139390 covers it (filters allowing more-specifics accept it). Add a route object with origin AS139390 in the RIR database for the space.3 of 673
ROA: none103.143.62.0/24No ROA covers it. Add a ROA for AS139390, maxLength 24.672 of 673
Route object: RIR103.143.62.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none103.143.63.0/24No ROA covers it. Add a ROA for AS139390, maxLength 24.672 of 673
Route object: RIR103.143.63.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none204.157.164.0/24No ROA covers it. Add a ROA for AS139390, maxLength 24.672 of 673
Route object: RIR204.157.164.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none204.157.165.0/24No ROA covers it. Add a ROA for AS139390, maxLength 24.672 of 673
Route object: RIR204.157.165.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none38.56.80.0/24No ROA covers it. Add a ROA for AS139390, maxLength 24.669 of 673
Route object: RIR38.56.80.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

38.172.152.0/23RADBNo ROA
103.143.62.0/23RADBNo ROA
204.157.164.0/23RADBNo ROA

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.