CipherStash Outage History

CipherStash is up right now

CipherStash had 2 outages in the last 2 years totaling 22h 7m of downtime — averaging 0.1 incidents per month.

There were 2 CipherStash outages since January 9, 2026 totaling 22h 7m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.cipherstash.com

Minor February 17, 2026

Elevated error rates on requests for OIDC federation requests to CTS

Detected by Pingoru
Feb 17, 2026, 02:00 AM UTC
Resolved
Feb 17, 2026, 08:12 AM UTC
Duration
6h 12m
Affected: CipherStash Cloud (CipherStash Cloud)
Timeline · 4 updates
  1. investigating Feb 17, 2026, 02:00 AM UTC

    We are observing elevated client-side error rates for OIDC federation requests. This is currently affecting a small (<5) number of customers. We are currently investigating this issue, and will post updates as we have them.

  2. investigating Feb 17, 2026, 05:25 AM UTC

    We have identified the condition causing the 400-series responses. We are debugging how JWTs in a specific format are failing strict validation.

  3. investigating Feb 17, 2026, 07:24 AM UTC

    He have identified the cause of the issue, and are deploying a fix. In a handful of JWTs, the header of the JWT being sent to CipherStash CTS includes a non-standard parameter that has a boolean value. While this is technically allowed under the RFC, a recently applied patch for...

  4. resolved Feb 17, 2026, 08:12 AM UTC

    We have deployed a fix, and the error rate has returned to zero. The incident is closed.

Read the full incident report →

Minor January 9, 2026

Memory leak in CipherStash Proxy when inserting encrypted JSON

Detected by Pingoru
Jan 09, 2026, 07:00 PM UTC
Resolved
Jan 10, 2026, 10:55 AM UTC
Duration
15h 55m
Affected: CipherStash Proxy (CipherStash Proxy)
Timeline · 7 updates
  1. investigating Jan 09, 2026, 07:00 PM UTC

    Some customers are experiencing a memory leak in CipherStash Proxy when inserting records into their databases.

  2. investigating Jan 10, 2026, 04:11 AM UTC

    We are able to reliably replicate the issue in Proxy, and have added a test case to the Proxy integration tests that is failing. Our current hypothesis is: Proxy's mapped statement cache is not releasing older cached statements. What is the mapped statement cache in...

  3. investigating Jan 10, 2026, 05:05 AM UTC

    We have disproved the mapped statement cache hypothesis. We are performing additional profiling to determine the source of the leak.

  4. investigating Jan 10, 2026, 06:21 AM UTC

    Our current hypothesis is: the memory leak is in cipherstash-client We are continuing to debug the exact cause, and our current focus is on the JSON indexer

  5. investigating Jan 10, 2026, 07:23 AM UTC

    We have validated the hypothesis, and the leak has been identified in the encrypted JSON index generation in cipherstash-client After plaintext JSON is indexed, the memory is being zeroized, but not freed We are working on a fix for it now, and will make new CipherStash...

  6. investigating Jan 10, 2026, 08:46 AM UTC

    We have implemented a fix to cipherstash-client, and released it in 0.31.1 We have upgraded CipherStash Proxy to use cipherstash-client 0.31.1 We...

  7. resolved Jan 10, 2026, 10:55 AM UTC

    Fix has been released in CipherStash Proxy 2.1.9. Customers using searchable encrypted JSON in CipherStash Proxy will need to upgrade to 2.1.9 to resolve this issue.

Read the full incident report →