Spacelift Outage History
Spacelift is up right nowSpacelift had 14 outages in the last 2 years totaling 34h 36m of downtime — averaging 0.6 incidents per month.
There were 14 Spacelift outages since May 27, 2025 totaling 34h 36m of downtime. Each is summarised below — incident details, duration, and resolution information.
Git clone operations failing with VCS agents
Timeline · 3 updates
- identified Apr 17, 2026, 01:45 PM UTC
A third party library update broke git operations when using a VCS agent. We are rolling out to the previous version.
- monitoring Apr 17, 2026, 02:25 PM UTC
A fix has been deployed to make sure git operations using VCS agents will operate correctly from now. We are still monitoring errors.
- resolved Apr 17, 2026, 03:02 PM UTC
This incident has been resolved.
Issues resolving correct module configuration when creating a new module version
Affected: Event processing
Timeline · 4 updates
- investigating Apr 14, 2026, 01:35 PM UTC
We're currently investigating the issue, and will provide an update soon.
- identified Apr 14, 2026, 02:04 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Apr 14, 2026, 02:08 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 14, 2026, 02:23 PM UTC
This incident has been resolved.
Spacelift Terraform Provider v1.47.0 incorrect signature
Timeline · 5 updates
- investigating Mar 31, 2026, 02:25 PM UTC
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.
- identified Mar 31, 2026, 02:28 PM UTC
We have identified the root cause to be in the goreleaser: https://github.com/goreleaser/goreleaser/issues/6514
- identified Mar 31, 2026, 02:32 PM UTC
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.
- monitoring Mar 31, 2026, 02:42 PM UTC
Version v1.47.1 released. We are waiting for registries to pick up the new version, then we will confirm the fix.
- resolved Mar 31, 2026, 02:45 PM UTC
We have confirmed the correct functionality of v1.47.1
Environment disruptions (app.us.spacelift.io)
Timeline · 4 updates
- monitoring Mar 16, 2026, 04:24 PM UTC
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.
- monitoring Mar 16, 2026, 05:09 PM UTC
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.
- monitoring Mar 16, 2026, 05:51 PM UTC
We are still facing ongoing issues with stuck runs in our US environment and are working on automatic remediation.
- resolved Mar 16, 2026, 08:03 PM UTC
The issue has been resolved
Trivy plugin failing with 404 error
Timeline · 3 updates
- identified Mar 02, 2026, 12:59 PM UTC
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.
- resolved Mar 02, 2026, 02:03 PM UTC
This incident has been resolved. See the postmortem for resolution instructions.
- postmortem Mar 02, 2026, 02:53 PM UTC
📣 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.
Elevated GitHub Error Rate
Affected: HTTP APIAPI Errors
Timeline · 2 updates
- monitoring Nov 18, 2025, 09:21 PM UTC
We are experiencing elevated error rates from API requests made to GitHub and are monitoring the situation.
- resolved Nov 18, 2025, 10:10 PM UTC
This incident has been resolved.
Event Processing Delays
Affected: Event processingWebhooks
Timeline · 4 updates
- investigating Oct 30, 2025, 08:30 PM UTC
We're seeing increased delays and/or elevated error rates in our event processing queue.
- identified Oct 30, 2025, 08:53 PM UTC
The root cause was asynchronous processing being throttled
- monitoring Oct 30, 2025, 08:55 PM UTC
We can see our action to have positive impact on the service. Number of queued messages is gradually decreasing.
- resolved Oct 30, 2025, 09:25 PM UTC
We think the impact from the issue is over.
Elevated API Errors
Affected: GraphQL APIEvent processingPlatform UI
Timeline · 2 updates
- monitoring Oct 17, 2025, 10:04 AM UTC
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.
- resolved Oct 17, 2025, 10:05 AM UTC
This incident has been resolved.
Spacelift unavailable
Affected: GraphQL APIEvent processing
Timeline · 2 updates
- investigating Aug 07, 2025, 01:23 PM UTC
A recent deployment has caused Spacelift to become unavailable. We are working on rolling back to a working version and will post an update as soon as that has been done.
- resolved Aug 07, 2025, 01:31 PM UTC
We have successfully resolved the deployment issue and Spacelift is available again.
Incident affecting run scheduling
Affected: Event processingPublic workers
Timeline · 4 updates
- investigating Jul 23, 2025, 08:39 AM UTC
We are currently investigating an incident affecting run scheduling and other asynchronous processing in Spacelift. The incident is causing delays with starting runs and updating statuses in VCS systems. As soon as we have more information we will post a further update.
- identified Jul 23, 2025, 08:49 AM UTC
The problem was caused by a large backlog of messages building up on one of our message queues. The backlog has cleared and the system appears to be operating correctly again. We are currently trying to understand the root cause to prevent it happening again.
- monitoring Jul 23, 2025, 09:40 AM UTC
We have identified the root cause of the incident. We are currently monitoring to make sure the system is stable, and we will take steps to prevent it occurring again.
- resolved Jul 23, 2025, 10:16 AM UTC
After continuing to monitor the system we have confirmed that it is stable again.
Invalid CANCELED Value in Stack List
Timeline · 3 updates
- identified Jun 27, 2025, 12:46 PM UTC
We've found the cause of stack list errors affecting a small number of customers. The issue relates to canceled runs on a stack. A fix is in progress.
- monitoring Jun 27, 2025, 01:58 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Jun 27, 2025, 02:13 PM UTC
This incident has been resolved.
Degradation of the GraphQL API
Timeline · 2 updates
Spacelift GraphQL API unavailable
Affected: GraphQL API
Timeline · 3 updates
- identified May 27, 2025, 09:18 AM UTC
We've identified an issue with our latest production deployment that is causing Spacelift to be unavailable. We are working on rolling out a fix and will update this page as soon as we have more information.
- monitoring May 27, 2025, 09:38 AM UTC
We have put in place a fix and are now monitoring it to make sure that the problem is fully resolved.
- resolved May 27, 2025, 10:05 AM UTC
We have not detected any issues in the past 30 minutes and are marking this incident as resolved. We will investigate exactly how this incident occurred to try to prevent a similar issue in future.