bgpreport

Network · data from 2026-11-12

AS38158 CBN Networks

Registry name: CBN-AS-ID - PT. Cyberindo Aditama, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38158, 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.91.22.0/24 Valid Nonecovered by 103.91.20.0/22 672 100% 66
121.100.2.0/24 Valid Nonecovered by 121.100.0.0/22 672 100% 67
121.100.6.0/24 Valid Nonecovered by 121.100.4.0/22 672 100% 67
103.91.20.0/22 Valid Other IRR onlyRADB 673 100% 68
121.100.0.0/21 Valid RIR databaseAPNIC, RADB 673 100% 68
121.100.0.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
121.100.4.0/22 Valid RIR databaseAPNIC, RADB 673 100% 68
2402:9800::/32 Valid RIR databaseAPNIC, RADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS38158: AS-NAPCBN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS38158 isn't in the set, or no route object for AS38158 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS38158 in itNot covered
AS-NAPCBN RADBlists itself further down15 member sets in no database: AS-ATHARVA, AS-BEIBI-AS-ID, AS-DETELNETWORKS-ID, AS-JOGLO-AS-ID, AS-LINTASDAYA-AS-ID … 1,414183209,002 Yes 0

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

  • Route object: none3
  • Route object: RIR1
  • AS-SET: missing member15
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none103.91.22.0/24No route object for it. A route object for 103.91.20.0/22 with origin AS38158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38158 in the RIR database for the space.672 of 673
Route object: none121.100.2.0/24No route object for it. A route object for 121.100.0.0/22 with origin AS38158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38158 in the RIR database for the space.672 of 673
Route object: none121.100.6.0/24No route object for it. A route object for 121.100.4.0/22 with origin AS38158 covers it (filters allowing more-specifics accept it). Add a route object with origin AS38158 in the RIR database for the space.672 of 673
Route object: RIR103.91.20.0/22Route object only in RADB. Add it in the RIR database for the space.673 of 673
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-ATHARVA; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-BEIBI-AS-ID; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-DETELNETWORKS-ID; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-JOGLO-AS-ID; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-LINTASDAYA-AS-ID; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-MTT-AS-ID; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-OAS-AS-ID; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-RAPDODGE:AS-AIRLINK; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS-TLINK-CUSTOMERS; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS149662:AS-HOSTNET; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS150238:AS-SHARTEL; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS150249:AS-ATHARVA; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS150501:AS-HCI; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS150552:AS-BAROKAHNET; no IRR database read has it.
AS-SET: missing memberAS-NAPCBNAS-NAPCBN (RADB) lists AS45723:AS-OMADATA; no IRR database read has it.

Route objects not announced

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

103.91.20.0/23RADBValid
103.91.20.0/24RADBValid
121.100.0.0/24APNICValid
2001:470:193::/48ARINValid

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.