Koyeb incident
Deployments failing for services using secrets with uppercase names
Resolved after 2 hours 43 minutes, affecting API and Build / Provisioning, on November 11, 2026.
Between 15:55 and 17:19 UTC on November 11, some new deployments failed with the error "Secrets do not exist". This affected deployments that reference a secret whose name contains uppercase letters, even though the secret exists. We identified the cause as a recent change to how secret references are validated, and rolled it back at 17:19 UTC. New deployments are now working normally. Services that were already running were not interrupted. If one of your deployments failed with "Secrets do not exist" during this window, please redeploy the service. No changes to your secrets or configuration are needed.
Affected components
Update timeline
- investigating Nov 11, 2026, 02:55 PM UTC
We implemented a fix and are currently monitoring the result.
- monitoring Nov 11, 2026, 04:19 PM UTC
Between 15:55 and 17:19 UTC on November 11, some new deployments failed with the error "Secrets do not exist". This affected deployments that reference a secret whose name contains uppercase letters, even though the secret exists. We identified the cause as a recent change to how secret references are validated, and rolled it back at 17:19 UTC. New deployments are now working normally. Services that were already running were not interrupted. If one of your deployments failed with "Secrets do not exist" during this window, please redeploy the service. No changes to your secrets or configuration are needed.
- resolved Nov 11, 2026, 05:38 PM UTC
This incident has been resolved.
Your product runs on more than Koyeb
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services