Skip to main content

list-cloud-incidents

dci list-cloud-incidents [flags]

Returns a list of all the active and historical cloud incidents for Google Cloud and Amazon Web Services. Incidents are returned in reverse chronological order by default.

CLI default view

dci list-cloud-incidents presents a curated table by default:

  • Columns: title, platform, product, status, and created (UTC) (from createTime).
  • In interactive tables, created (UTC) renders in your local timezone and is titled created (local); machine formats, agent mode, and --utc keep UTC — see Timestamps and timezones.
  • --output json and explicit -C/--fields selections return the raw fields documented below.

Flags

--max-results: (integer format:int64 default:50)

--page-token: (string)

--filter: (string)

--min-creation-time: (string)

--max-creation-time: (string)

Output

OK - The request succeeded.

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

FieldTypeDescription
incidentsarray of objectArray of cloud incidents
incidents[].createTimeinteger (int64)The creation time of this cloud incident, in milliseconds since the epoch.
incidents[].idstringThe unique cloud incident identifier.
incidents[].platformstringThe Cloud Platform. One of: "google-cloud", "amazon-web-services", "microsoft-azure".
incidents[].productstringThe name of the product affected by the cloud incident
incidents[].statusstringThe Status of the issue One of: "active", "archived".
incidents[].titlestringCloud incident name as provided by the cloud platform vendor
pageTokenstringPage token, returned by a previous call, to request the next page of results
rowCountinteger (int64)Cloud incidents rows count
Raw JSON schema
{
"type": "object",
"properties": {
"incidents": {
"type": "array",
"description": "Array of cloud incidents",
"items": {
"type": "object",
"description": "Summary information for a cloud incident.",
"properties": {
"createTime": {
"type": "integer",
"description": "The creation time of this cloud incident, in milliseconds since the epoch.",
"format": "int64"
},
"id": {
"type": "string",
"description": "The unique cloud incident identifier."
},
"platform": {
"type": "string",
"description": "The Cloud Platform.",
"enum": [
"google-cloud",
"amazon-web-services",
"microsoft-azure"
]
},
"product": {
"type": "string",
"description": "The name of the product affected by the cloud incident"
},
"status": {
"type": "string",
"description": "The Status of the issue",
"enum": [
"active",
"archived"
]
},
"title": {
"type": "string",
"description": "Cloud incident name as provided by the cloud platform vendor"
}
}
}
},
"pageToken": {
"type": "string",
"description": "Page token, returned by a previous call, to request the next page of results"
},
"rowCount": {
"type": "integer",
"description": "Cloud incidents rows count",
"format": "int64"
}
}
}

Errors

On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.

HTTP statusExit codeError codeMeaning
40030VALIDATION_ERRORThe arguments or request body were rejected. Review the command's flags and payload.
40110AUTHENTICATION_FAILEDNot signed in, or the API token is invalid. Run dci login or check DCI_API_KEY.
40311PERMISSION_DENIEDThe DoiT user or the active customer context does not have access.
40420RESOURCE_NOT_FOUNDThe requested resource does not exist. Check the identifier argument.

Aliases: list-known-issues