bgpreport

Network · data from 2026-11-12

AS58558 Jagat Media Teknologi

Registry name: IDNIC-WIJAYASOLUSINDO-AS-ID - PT Jagat Media Teknologi, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS58558, 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.196.47.0/24 No ROA Other origin only 673 100% 69
103.196.43.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
103.196.46.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
103.237.32.0/22 No ROA Other IRR onlyNTTCOM 673 100% 68
103.237.32.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
103.237.32.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
103.237.33.0/24 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
103.237.34.0/23 No ROA Other IRR onlyNTTCOM, RADB 673 100% 68
103.237.34.0/24 No ROA Other IRR onlyNTTCOM 673 100% 68
103.237.35.0/24 No ROA Other IRR onlyNTTCOM 673 100% 68
43.230.5.0/24 No ROA RIR databaseAPNIC 673 100% 68

AS-SET

AS58558'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 21 are in fix.csv.

  • ROA: none11
  • Route object: none1
  • Route object: RIR9
ChangePrefix or setDetailFull-table peers
ROA: none103.196.47.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673
Route object: none103.196.47.0/24Route objects for it name AS58823, AS142362. Add a route object with origin AS58558 in the RIR database for the space.673 of 673
ROA: none103.196.43.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673
Route object: RIR103.196.43.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.196.46.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673
Route object: RIR103.196.46.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.237.32.0/22No ROA covers it. Add a ROA for AS58558, maxLength 22.673 of 673
Route object: RIR103.237.32.0/22Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none103.237.32.0/23No ROA covers it. Add a ROA for AS58558, maxLength 23.673 of 673
Route object: RIR103.237.32.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.237.32.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673
Route object: RIR103.237.32.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.237.33.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673
Route object: RIR103.237.33.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.237.34.0/23No ROA covers it. Add a ROA for AS58558, maxLength 23.673 of 673
Route object: RIR103.237.34.0/23Route object only in NTTCOM, RADB. Add it in the RIR database for the space.673 of 673
ROA: none103.237.34.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673
Route object: RIR103.237.34.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none103.237.35.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673
Route object: RIR103.237.35.0/24Route object only in NTTCOM. Add it in the RIR database for the space.673 of 673
ROA: none43.230.5.0/24No ROA covers it. Add a ROA for AS58558, maxLength 24.673 of 673

Route objects not announced

Every route object with origin AS58558 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.