docs: add info about status page

Author: dangrondahl

docs.kosli.com/content/tutorials/what_do_i_do_if_kosli_is_down.md

@@ -1,8 +1,8 @@
 ---
-title: "What do I do if Kosli is down?"
+title: 'What do I do if Kosli is down?'
 bookCollapseSection: false
 weight: 507
-summary: "Customers use Kosli to attest evidence of their business and software processes. If Kosli is down, these attestations will fail. In this situation there is a built-in mechanism to instantly turn Kosli off and keep the pipelines flowing. When Kosli is back up, you can instantly turn Kosli back on."
+summary: 'Customers use Kosli to attest evidence of their business and software processes. If Kosli is down, these attestations will fail. In this situation there is a built-in mechanism to instantly turn Kosli off and keep the pipelines flowing. When Kosli is back up, you can instantly turn Kosli back on.'
 ---
 
 # What do I do if Kosli is down?
@@ -13,29 +13,33 @@ This will break CI workflow pipelines, blocking artifacts from being deployed.
 In this situation there is a built-in mechanism to instantly turn Kosli off and keep the pipelines flowing.
 When Kosli is back up, you can instantly turn Kosli back on.
 
+{{% hint info %}}
+You can check the current status of Kosli services at https://status.app.kosli.com or by running `kosli status` in the CLI.
+{{% /hint %}}
+
 ## Turning Kosli CLI calls on and off instantly
 
 If the `KOSLI_DRY_RUN` environment variable is set to `true` then all Kosli CLI commands will:
-* Not communicate with Kosli at all
-* Print the payload they would have sent
-* Exit with a zero status code
+
+- Not communicate with Kosli at all
+- Print the payload they would have sent
+- Exit with a zero status code
 
 We recommend creating an Org-level KOSLI_DRY_RUN variable in your CI system and, in all CI workflows,
-ensuring there is an environment variable set from it. 
+ensuring there is an environment variable set from it.
 
 For example, in a [Github Action workflow](https://github.com/cyber-dojo/differ/blob/main/.github/workflows/main.yml):
 
 ```yaml
 name: Main
-...
+---
 env:
-  KOSLI_DRY_RUN: ${{ vars.KOSLI_DRY_RUN }}           # true iff Kosli is down
+  KOSLI_DRY_RUN: ${{ vars.KOSLI_DRY_RUN }} # true iff Kosli is down
 ```
 
-
 ## Turning Kosli API calls on and off instantly
 
-If you are using the Kosli API in your workflows (e.g. using `curl`), we recommend using the same Org-level `KOSLI_DRY_RUN` 
+If you are using the Kosli API in your workflows (e.g. using `curl`), we recommend using the same Org-level `KOSLI_DRY_RUN`
 environment variable and guarding the `curl` call with a simple if statement. For example:
 
 ```shell
@@ -54,7 +58,3 @@ kosli_curl()
   fi
 }
 ```
-
-
-
-