Network · data from 2026-11-12
AS137331 Cloud Teknologi Nusantara
Registry name: IDNIC-CLOUDTEKNOLOGI-AS-ID - PT Cloud Teknologi Nusantara, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS137331, 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:df6:efc0::/48 | No ROA | Other IRR onlyRADB | 634 100% |
| 103.102.15.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 103.157.116.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 103.186.208.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 163.128.238.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 103.133.222.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 103.133.223.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 670 100% |
| 103.157.116.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.157.117.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 163.128.238.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 163.128.239.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 103.178.174.0/23 | Valid | Other IRR onlyRADB | 669 99% |
| 103.178.174.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 103.178.175.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 2001:df4:b100::/48 | Valid | Other IRR onlyALTDB, RADB, RIPE-NONAUTH | 635 100% |
| 103.133.222.0/23 | Valid | RIR databaseAPNIC, RADB | 673 100% |
| 103.112.162.0/23 | Valid | RIR databaseAPNIC, RADB, RIPE-NONAUTH | 672 100% |
| 103.112.162.0/24 | Valid | RIR databaseAPNIC, RADB, RIPE-NONAUTH | 670 100% |
| 103.112.163.0/24 | Valid | RIR databaseAPNIC, RADB, RIPE-NONAUTH | 670 100% |
| 178.83.163.0/24 | Valid | RIR databaseRADB, RIPE | 669 99% |
AS-SET
PeeringDB's irr_as_set for AS137331: AS137331:AS-CLOUDTEKNOLOGI. 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 (AS137331 isn't in the set, or no route object for AS137331 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.
| Name | Database | ASNs | Sets | AS137331 in it | Not covered |
|---|---|---|---|---|---|
| AS137331:AS-CLOUDTEKNOLOGI | RADB1 member set in no database: AS150238:AS-SHARTEL | 54 | 3 | Yes | 0 |
| APNIC (also)2 member sets in no database: AS-BERTUAHIX, AS-CMEDIA | 6 | 1 | 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 20 are in fix.csv.
- ROA: none1
- Route object: RIR15
- AS-SET: missing member1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:df6:efc0::/48 | No ROA covers it. Add a ROA for AS137331, maxLength 48. |
| Route object: RIR | 2001:df6:efc0::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.102.15.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.157.116.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.186.208.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 163.128.238.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.133.222.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.133.223.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.157.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.157.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 163.128.238.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 163.128.239.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.178.174.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.178.174.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.178.175.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2001:df4:b100::/48 | Route object only in ALTDB, RADB, RIPE-NONAUTH. Add it in the RIR database for the space. |
| AS-SET: missing member | AS137331:AS-CLOUDTEKNOLOGI | AS137331:AS-CLOUDTEKNOLOGI (RADB) lists AS150238:AS-SHARTEL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS137331 whose prefix no peer sees AS137331 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 103.186.208.0/23 | RADB | No ROA |
| 2406:a0c0::/32 | RADB | Valid |
| 2602:fd92:c10::/44 | ARIN, RADB | Valid |
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.