bgpreport

Network · data from 2026-11-12

AS141968 Industri Kreatif Digital

Registry name: IDNIC-IKADA-AS-ID - PT Industri Kreatif Digital, ID · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS141968, 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.

2407:6ac0:10::/48 Valid None 634 100% 67
2407:6ac0:11::/48 Valid None 634 100% 67
82.153.126.0/24 Valid Other IRR onlyRADB 672 100% 70
82.153.226.0/24 Valid Other IRR onlyRADB 672 100% 70
103.42.117.0/24 Valid Other IRR onlyRADB 672 100% 70
103.177.95.0/24 Valid Other IRR onlyRADB 672 100% 70
103.180.124.0/24 Valid Other IRR onlyRADB 672 100% 70
103.180.125.0/24 Valid Other IRR onlyRADB 672 100% 70
109.111.52.0/24 Valid Other IRR onlyRADB 672 100% 70
109.111.53.0/24 Valid Other IRR onlyRADB 672 100% 70
109.176.17.0/24 Valid Other IRR onlyRADB 672 100% 70
162.4.17.0/24 Valid Other IRR onlyRADB 672 100% 70
103.42.116.0/24 Valid Other IRR onlyRADB 655 97% 68
103.177.94.0/24 Valid Other IRR onlyRADB 655 97% 68
2407:6ac0:2::/48 Valid Other IRR onlyRADB 635 100% 67
2407:6ac0:4::/48 Valid Other IRR onlyRADB 635 100% 67
2407:6ac0:5::/48 Valid Other IRR onlyRADB 635 100% 67
2407:6ac0:7::/48 Valid Other IRR onlyRADB 635 100% 67
2407:6ac0:8::/48 Valid Other IRR onlyRADB 635 100% 67
2407:6ac0:9::/48 Valid Other IRR onlyRADB 635 100% 67
2407:6ac0:1::/48 Valid Other IRR onlyRADB 634 100% 67
2407:6ac0:3::/48 Valid Other IRR onlyRADB 634 100% 67
2407:6ac0:6::/48 Valid Other IRR onlyRADB 634 100% 67
2407:6ac0:12::/48 Valid Other IRR onlyRADB 634 100% 67
82.25.62.0/24 Valid RIR databaseRADB, RIPE 673 100% 69
103.167.35.0/24 Valid RIR databaseAPNIC, RADB 673 100% 69
31.59.119.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
45.66.153.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
45.149.187.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
45.158.126.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
85.209.163.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
98.142.245.0/24 Valid RIR databaseARIN, RADB 672 100% 70
103.167.34.0/24 Valid RIR databaseAPNIC, RADB 672 100% 70
109.105.194.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
141.11.25.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
141.11.160.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
141.11.190.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
151.243.222.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
151.245.85.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
178.248.73.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
194.34.255.0/24 Valid RIR databaseRADB, RIPE 672 100% 70
207.180.19.0/24 Valid RIR databaseARIN, RADB 671 100% 70
217.216.146.0/24 Valid RIR databaseRADB, RIPE 671 100% 70
217.217.46.0/24 Valid RIR databaseRADB, RIPE 670 100% 70
103.119.237.0/24 Valid RIR databaseAPNIC, RADB 655 97% 68
185.205.222.0/24 Valid RIR databaseRADB, RIPE 655 97% 68

AS-SET

PeeringDB's irr_as_set for AS141968: AS141968:AS-SET-IKADA-ID. 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 (AS141968 isn't in the set, or no route object for AS141968 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 objectsAS141968 in itNot covered
AS141968:AS-SET-IKADA-ID RADB 151218 Yes 2
APNIC (also)1 member set in no database: AS141120:AS-SET-WARNAHOST-AS-ID 131213 Yes 2

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

  • Route object: none2
  • Route object: RIR22
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none2407:6ac0:10::/48No route object for it. Add a route object with origin AS141968 in the RIR database for the space.634 of 636
Route object: none2407:6ac0:11::/48No route object for it. Add a route object with origin AS141968 in the RIR database for the space.634 of 636
Route object: RIR82.153.126.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR82.153.226.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.42.117.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.177.95.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.180.124.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.180.125.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR109.111.52.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR109.111.53.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR109.176.17.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR162.4.17.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.42.116.0/24Route object only in RADB. Add it in the RIR database for the space.655 of 673
Route object: RIR103.177.94.0/24Route object only in RADB. Add it in the RIR database for the space.655 of 673
Route object: RIR2407:6ac0:2::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2407:6ac0:4::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2407:6ac0:5::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2407:6ac0:7::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2407:6ac0:8::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2407:6ac0:9::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2407:6ac0:1::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2407:6ac0:3::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2407:6ac0:6::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2407:6ac0:12::/48Route object only in RADB. Add it in the RIR database for the space.634 of 636

Route objects not announced

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

2.153.126.0/24RADBNo ROA
45.198.36.0/22RADBNo ROA
45.198.36.0/23RADBNo ROA
45.198.38.0/23RADBNo ROA
103.167.34.0/23APNIC, RADBNo ROA
103.177.94.0/23RADBValid
103.180.124.0/23RADBValid
109.111.52.0/23RADB, RIPEValid
191.222.34.0/23RADB, RIPEValid

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.