CipherStash Outage History
CipherStash is up right nowPingoru has recorded 2 incidents for CipherStash: 2 in the last 12 months and 0 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 0 | 0 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 0 | 0 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 0 | 0 of 744 (0%) |
| November 2026 | 0 | 0 of 79 (0%) |
Incidents, newest first
Minor February 17, 2026 Elevated error rates on requests for OIDC federation requests to CTS 6h 12m CipherStash Cloud
Started Feb 17, 2026, 02:00 AM UTC· resolved Feb 17, 2026, 08:12 AM UTC
- 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.
- 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.
- 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 stricter validation of JWT header parameters is causing these JWTs to be rejected. We are deploying a fix, and expect to see error rates drop in the next 30 minutes.
- 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.
Minor January 9, 2026 Memory leak in CipherStash Proxy when inserting encrypted JSON 15h 55m CipherStash Proxy
Started Jan 09, 2026, 07:00 PM UTC· resolved Jan 10, 2026, 10:55 AM UTC
- investigating Jan 09, 2026, 07:00 PM UTC
Some customers are experiencing a memory leak in CipherStash Proxy when inserting records into their databases.
- 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 Proxy? It contains the analysed and mapped statements from the initial query parse step It does not contain any encrypted data — only parameterised SQL
- 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.
- 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
- 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 Proxy release available soon
- 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 are about to release a new version of CipherStash Proxy that includes the patch To resolve this issue, affected customers will need to upgrade to the latest CipherStash Proxy
- 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.