bgpreport

Network · data from 2026-11-12

AS141892 IDNIC-SENGKED-AS-ID - CV Andhika Pratama Sanggoro

Registry name: IDNIC-SENGKED-AS-ID - CV Andhika Pratama Sanggoro, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141892, 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.
89.21.85.0/24 Invalid: origin Other origin only 3 0%low visibility 2
103.163.161.0/24 Valid Other IRR onlyRADB 673 100% 69
103.186.30.0/23 Valid Other IRR onlyRADB 673 100% 69
103.186.30.0/24 Valid Other IRR onlyRADB 673 100% 69
103.186.31.0/24 Valid Other IRR onlyRADB 673 100% 69
157.66.54.0/23 Valid Other IRR onlyRADB 673 100% 69
157.66.54.0/24 Valid Other IRR onlyRADB 673 100% 69
157.66.55.0/24 Valid Other IRR onlyRADB 673 100% 69
202.73.25.0/24 Valid Other IRR onlyRADB 673 100% 69
202.73.26.0/24 Valid Other IRR onlyRADB 673 100% 69
31.56.56.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
110.50.82.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
212.69.6.0/24 Valid RIR databaseRADB, RIPE 673 100% 69

AS-SET

AS141892 isn't in PeeringDB, where networks name their 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 13 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: RIR9
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin89.21.85.0/24ROAs covering it name AS198468, not AS141892. If AS141892 should announce it, add a ROA for AS141892.3 of 673
Route object: none89.21.85.0/24Route objects for it name AS198468. Add a route object with origin AS141892 in the RIR database for the space.3 of 673
Route object: RIR103.163.161.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.186.30.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.186.30.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.186.31.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.66.54.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.66.54.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR157.66.55.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.73.25.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR202.73.26.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

2001:df6:4e80::/48ALTDBNo ROA
2a0f:85c1:3c6::/48RIPEValid

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.