CipherStash incident

Elevated error rates on requests for OIDC federation requests to CTS

Resolved after 6 hours 12 minutes, affecting CipherStash Cloud, on February 17, 2026.

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.

Started
Feb 17, 2026, 02:00 AM UTC
Resolved
Feb 17, 2026, 08:12 AM UTC
Duration
6h 12m
Detected by Pingoru
Feb 17, 2026, 02:00 AM UTC

Affected components

CipherStash Cloud

Update timeline

  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 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.

  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.

Your product runs on more than CipherStash

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →