bgpreport

Network · data from 2026-11-12

AS132644 IDNIC-CBNCLOUD-AS-ID - PT. Cyberindo Mega Persada

Registry name: IDNIC-CBNCLOUD-AS-ID - PT. Cyberindo Mega Persada, ID · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132644, 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.
2001:df2:c000::/48 No ROA Other IRR onlyRADB 635 100% 70
45.126.132.0/22 Valid Other IRR onlyRADB 673 100% 69
103.24.12.0/23 Valid Other IRR onlyRADB 673 100% 69
103.253.68.0/23 Valid Other IRR onlyRADB 673 100% 69
116.204.128.0/24 Valid Other IRR onlyRADB 673 100% 69
116.204.129.0/24 Valid Other IRR onlyRADB 673 100% 69
116.204.130.0/24 Valid Other IRR onlyRADB 673 100% 69
116.204.131.0/24 Valid Other IRR onlyRADB 673 100% 69
116.204.248.0/23 Valid Other IRR onlyRADB 673 100% 69
116.204.250.0/23 Valid Other IRR onlyRADB 673 100% 69

AS-SET

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

  • ROA: none1
  • Route object: RIR10
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none2001:df2:c000::/48No ROA covers it. Add a ROA for AS132644, maxLength 48.635 of 636
Route object: RIR2001:df2:c000::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR45.126.132.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.24.12.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR103.253.68.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.204.128.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.204.129.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.204.130.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.204.131.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.204.248.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR116.204.250.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

116.204.128.0/22RADBNo ROA
116.204.128.0/23RADBNo ROA
116.204.130.0/23RADBNo ROA
116.204.248.0/22RADBNo 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.