Spacelift had 12 outages in the last 2 years totaling 105h 58m of downtime — averaging 0.5 incidents per month.
There were 12 Spacelift outages since October 17, 2025 totaling 105h 58m of downtime. Each is summarised below — incident details, duration, and resolution information.
We're seeing increased delays and/or elevated error rates in our FedRamp event processing queue. The root cause has been identified, we working on restoring the regular functionality of the system.
We have restored events processing to the usual state. The root cause was a change that we released earlier today.
We are experiencing failing AWS API calls for runs using hashicorp/aws provider with version v6.57.0.
We have identified a problem with v6.57.0 of the hashicorp/aws provider causing requests for certain resources to fail. A workaround for affected customers is to pin to v6.56.0 or below. More details can be found on the HashiCorp status page: https://status.hashicorp.com/incidents/01KYPY1KTBE8KWC4E75RXN0XX8
This incident has been resolved.
We have identified an issue with external symlink configurations affecting some setups. Please contact Support if you are affected.
The incident has been resolved.
We've spotted as issue with failing runs. We're currently investigating the issue, and will provide an update soon.
The issue has been identified. This is not affecting public workers; only private workers can be affected. The last working version of the worker's image is [v1.79.0](https://github.com/spacelift-io/spacelift-worker-image/releases/tag/1.79.0). Please rollback to that version if you see failing runs after an update.
As a mitigation we have deregistered all of the AMIs for version 1.80.0 and 1.81.0. We are currently working on building new images that include a fix for the problem.
This incident has been resolved. A [new version](https://github.com/spacelift-io/spacelift-worker-image/releases/tag/1.82.0) of the image has been released.
A third party library update broke git operations when using a VCS agent. We are rolling out to the previous version.
A fix has been deployed to make sure git operations using VCS agents will operate correctly from now. We are still monitoring errors.
This incident has been resolved.
We're currently investigating the issue, and will provide an update soon.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We've spotted that Spacelift Terraform Provider version v1.47.0 has incorrect signature. We're currently investigating the issue, and will provide an update soon.
We have identified the root cause to be in the goreleaser: https://github.com/goreleaser/goreleaser/issues/6514
We have pinned goreleaser to an older version, and we are releasing an updated version of our provider (v1.47.1) with a correct signature.
Version v1.47.1 released. We are waiting for registries to pick up the new version, then we will confirm the fix.
We have confirmed the correct functionality of v1.47.1
We identified that an infrastructure change resulting in disruptions for US accounts, such as workers disconnecting from Spacelift and webhook-triggered runs not being processed. The main issue has been resolved, and message processing has recovered. Only US region customers were impacted.
We identified an infrastructure change that caused disruptions for US accounts, including workers disconnecting from Spacelift and webhook-triggered runs not being processed. The main issue has been resolved, and message processing has recovered. Only customers in the US region were impacted.
We are still facing ongoing issues with stuck runs in our US environment and are working on automatic remediation.
The issue has been resolved
The Trivy Spacelift plugin is currently causing runs to fail during the Initializing phase due to a security incident from Trivy (https://github.com/aquasecurity/trivy/discussions/10265) that caused GitHub release artifacts to be deleted. We have identified the issue and are currently working on deploying a fix.
This incident has been resolved. See the postmortem for resolution instructions.
📣 Trivy Plugin Action Required If you're using the previous version of the Trivy plugin, runs may fail during initialization due to missing release artifacts following a security incident in the upstream Trivy project \(details here: [https://github.com/aquasecurity/trivy/discussions/10265](https://github.com/aquasecurity/trivy/discussions/10265)\). We've updated the Spacelift Trivy plugin to **v0.69.2** and rolled the fix out to production - everything is now working as expected. To make sure your stacks use the updated version: 1. Go to **Plugins → Account plugins** and delete the existing Trivy plugin 2. Go to **Plugins → Templates** and install the Trivy plugin again Once done, all new runs will automatically use the fixed version. Thanks for your patience, and as always, reach out to support if you need anything.
We are experiencing elevated error rates from API requests made to GitHub and are monitoring the situation.
This incident has been resolved.
We deployed a change that caused database-related issues. This resulted in a 11 minute outage. The problem was automatically resolved by our deployment process.
This incident has been resolved.