Status page with history in Container and cloud workload security
A status page without past incidents tells you nothing about reliability.
4 of 27 companies we measured here publish it, that is 15%. Last checked 2026-10-19.
15% here against 17% across every category we measure. Container and cloud workload security sits below the overall share for this criterion.
This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.
Back to Status page with history across all categories, or to Container and cloud workload security.
- Found4
- Not found at checked addresses23
- Not measured1
28 companies in total. Unmeasured companies are excluded from the published share.
Published
A public status page with incident history.
| Vendor | What we found |
|---|---|
| Armo | https://status.armosec.io/Checked |
| Endor Labs | https://status.endorlabs.com/Checked |
| Socket | https://status.socket.dev/Checked |
| Upwind | https://status.upwind.io/Checked |
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 checkedChecked |
| Cast AI | 3 addresses checkedChecked |
| Chainguard | 3 addresses checkedChecked |
| Cloudsmith | 3 addresses checkedChecked |
| Docker Scout | 3 addresses checkedChecked |
| Fairwinds | 3 addresses checkedChecked |
| Falco | 3 addresses checkedChecked |
| Isovalent | 3 addresses checkedChecked |
| Kubescape | 3 addresses checkedChecked |
| Kubex | 3 addresses checkedChecked |
| Kyverno | 3 addresses checkedChecked |
| Nirmata | 3 addresses checkedChecked |
| Prisma Cloud | 3 addresses checkedChecked |
| Rafay | 3 addresses checkedChecked |
| Sedai | 3 addresses checkedChecked |
| Spectro Cloud | 3 addresses checkedChecked |
| Stackrox | 3 addresses checkedChecked |
| Sweet Security | 3 addresses checkedChecked |
| Tetragon | 3 addresses checkedChecked |
| Tigera | 3 addresses checkedChecked |
| Trivy | 3 addresses checkedChecked |
| vCluster | 3 addresses checkedChecked |
| Zesty | 3 addresses checkedChecked |
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.Checked |
Other criteria in Container and cloud workload security
- Data processing agreement
- Subprocessor list
- Data location stated
- Public pricing
- Certifications named
- Uptime SLA with a figure
- HTTPS enforced with HSTS
- No third-party tracking before consent
- security.txt (RFC 9116)
- Notice before subprocessors change
- Named privacy contact
Status page with history in related categories
Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.