bgpreport

Network · data from 2026-11-12

AS149359 Persada Data Multimedia

Registry name: IDNIC-PDM-AS-ID - PT Persada Data Multimedia, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149359, 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.169.0.0/24 No ROA None 218 32% 62
103.169.1.0/24 No ROA None 218 32% 62
49.0.26.0/24 Valid Other IRR onlyRADB 673 100% 69
103.176.107.0/24 Valid Other IRR onlyRADB 673 100% 69
103.180.118.0/24 Valid Other IRR onlyRADB 673 100% 70
103.215.71.0/24 Valid Other IRR onlyRADB 673 100% 70
49.0.27.0/24 Valid Other IRR onlyRADB 671 100% 69
103.180.119.0/24 Valid Other IRR onlyRADB 670 100% 70
2401:5ee0::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:1000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:2000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:3000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:4000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:5000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:6000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:7000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:8000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:9000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:a000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:b000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:c000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:d000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:e000::/36 Valid Other IRR onlyRADB 635 100% 70
2401:5ee0:f000::/36 Valid Other IRR onlyRADB 635 100% 70
103.19.78.0/24 Valid RIR databaseAPNIC 673 100% 70
103.19.79.0/24 Valid RIR databaseAPNIC 673 100% 70

AS-SET

AS149359'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 31 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: RIR22
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none103.169.0.0/24No ROA covers it. Add a ROA for AS149359, maxLength 24.218 of 673
Route object: none103.169.0.0/24No route object for it. Add a route object with origin AS149359 in the RIR database for the space.218 of 673
ROA: none103.169.1.0/24No ROA covers it. Add a ROA for AS149359, maxLength 24.218 of 673
Route object: none103.169.1.0/24No route object for it. Add a route object with origin AS149359 in the RIR database for the space.218 of 673
Route object: RIR49.0.26.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.176.107.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.180.118.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.215.71.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR49.0.27.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.180.119.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2401:5ee0::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:1000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:2000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:3000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:4000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:5000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:6000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:7000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:8000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:9000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:a000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:b000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:c000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:d000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:e000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2401:5ee0:f000::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

49.0.26.0/23RADBValid
103.17.78.0/23RADBNo ROA
103.19.78.0/23APNICValid
103.180.118.0/23RADBValid
2401:5ee0::/32RADBValid

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.