Status page with history in Container and cloud workload security
A status page without past incidents tells you nothing about reliability.
1 of 9 vendors we measured here publish it, that is 11%. Last checked 2026-09-02.
11% here against 29% across every category we measure. Container and cloud workload security sits below the overall share for this criterion.
Back to Status page with history across all categories, or to Container and cloud workload security.
Published
A public status page with incident history.
| Vendor | What we found |
|---|---|
| Armo | https://status.armosec.io/ |
No public status page found.
We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.
| Vendor | What we found |
|---|---|
| Anchore | 3 addresses checked |
| Cast AI | 3 addresses checked |
| Chainguard | 3 addresses checked |
| Cloudsmith | 3 addresses checked |
| Kubescape | 3 addresses checked |
| Prisma Cloud | 3 addresses checked |
| Sweet Security | 3 addresses checked |
| Trivy | 3 addresses checked |
Not measured
We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.
| Vendor | What we found |
|---|---|
| Clair | The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured. |
Found something we missed? Tell us and the next run picks it up.