Network · data from 2026-11-12
AS131717 Citra Jelajah Informatika
Registry name: IDNIC-CIFO-AS-ID - PT Citra Jelajah Informatika, ID · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS131717, 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.
| 45.118.112.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 45.118.113.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 45.118.114.0/24 | Valid | Other IRR onlyNTTCOM, REACH | 673 100% |
| 103.14.20.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.14.21.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.25.166.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.25.167.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.110.8.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.110.9.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 103.110.10.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.110.11.0/24 | Valid | Other IRR onlyNTTCOM | 673 100% |
| 103.184.98.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 103.184.99.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 115.178.51.0/24 | Valid | Other IRR onlyRADB | 673 100% |
| 115.178.52.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 115.178.53.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 115.178.54.0/24 | Valid | Other IRR onlyNTTCOM, RADB | 673 100% |
| 2401:10c0::/32 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 2401:10c0::/34 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 2401:10c0:4000::/34 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 2401:10c0:8000::/34 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 2401:10c0:c000::/34 | Valid | Other IRR onlyNTTCOM | 635 100% |
| 45.118.115.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS131717: AS131717:AS-CIFO. 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 (AS131717 isn't in the set, or no route object for AS131717 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 | AS131717 in it | Not covered |
|---|---|---|---|---|---|
| AS131717:AS-CIFO | APNIC | 7 | 1 | No | 23 |
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 51 are in fix.csv.
- Route object: RIR22
- AS-SET: own ASN1
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.118.112.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.118.113.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 45.118.114.0/24 | Route object only in NTTCOM, REACH. Add it in the RIR database for the space. |
| Route object: RIR | 103.14.20.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.14.21.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.25.166.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.25.167.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.110.8.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.110.9.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.110.10.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.110.11.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.184.98.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 103.184.99.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.51.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.52.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.53.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 115.178.54.0/24 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2401:10c0::/32 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2401:10c0::/34 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2401:10c0:4000::/34 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2401:10c0:8000::/34 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 2401:10c0:c000::/34 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS131717:AS-CIFO | AS131717 isn't in AS131717:AS-CIFO (APNIC) once expanded. Add AS131717 to it. |
Route objects not announced
Route objects with origin AS131717 whose prefix no peer sees AS131717 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.118.112.0/23 | NTTCOM, RADB | Valid |
| 45.118.114.0/23 | RADB | Valid |
| 103.7.52.0/23 | REACH | No ROA |
| 103.8.238.0/24 | REACH | Invalid: origin |
| 103.14.20.0/23 | APNIC, NTTCOM, RADB | Valid |
| 103.18.117.0/24 | REACH | Invalid: origin |
| 103.25.166.0/23 | APNIC | Valid |
| 103.53.76.0/24 | REACH | Invalid: origin |
| 103.53.77.0/24 | REACH | Invalid: origin |
| 103.53.78.0/24 | REACH | Invalid: origin |
| 103.53.79.0/24 | REACH | Invalid: origin |
| 103.55.33.0/24 | REACH | Invalid: origin |
| 103.64.15.0/24 | REACH | Invalid: origin |
| 103.110.8.0/22 | NTTCOM | Valid |
| 103.184.98.0/23 | RADB | Valid |
| 103.200.128.0/22 | RADB | No ROA |
| 103.212.211.0/24 | REACH | No ROA |
| 103.227.148.0/24 | REACH | Invalid: origin |
| 103.227.149.0/24 | REACH | Invalid: origin |
| 120.89.92.0/24 | REACH | Invalid: origin |
| 120.89.93.0/24 | REACH | Invalid: origin |
| 155.178.50.0/24 | NTTCOM | No ROA |
| 155.178.51.0/24 | NTTCOM | No ROA |
| 202.3.14.0/24 | RADB | No ROA |
| 203.153.20.0/24 | REACH | Invalid: origin |
| 203.153.21.0/24 | REACH | Invalid: origin |
| 203.153.22.0/24 | REACH | Invalid: origin |
| 203.153.23.0/24 | REACH | Invalid: origin |
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.