Spacelift Outage History

Spacelift is up right now

There were 6 Spacelift outages since March 2, 2026 totaling 28h 42m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://spacelift.statuspage.io

Major April 20, 2026

Terraform runs failing due to expired HashiCorp signing key

Detected by Pingoru
Apr 20, 2026, 11:43 AM UTC
Resolved
Apr 21, 2026, 09:20 AM UTC
Duration
21h 36m
Timeline · 3 updates
  1. monitoring Apr 20, 2026, 11:43 AM UTC

    We identified that Terraform runs were failing when downloading the Terraform binary. The public GPG key we use to verify HashiCorp's checksum signatures had expired, causing every binary download to fail signature verification. Runs using OpenTofu or a Custom workflow were not affected. A fix updating the embedded HashiCorp public key has been rolled out during the week-end across our managed infrastructure. If you are using private worker pools, you will need to cycle your worker pool so the workers pick up the latest launcher version that includes the fix. Until workers are cycled, new Terraform runs on those pools will continue to fail. Action required for Self-Hosted: Hotfix v5.1.1 has been published and can be used to resolve the issue on Self-Hosted installations on v5.1.0. If you are on an older Self-Hosted version, please contact your Spacelift account team — we are publishing targeted hotfixes on request. If you cannot upgrade right now, you can unblock Terraform runs by: - Switch from Terraform to OpenTofu if you can. - Switch to a custom workflow for your stack and provide Terraform binary yourself - Setting "skipVendorBinaryDownload: true" on the affected stacks, and running those stacks in a runner image that already has the terraform binary installed at the expected path.

  2. monitoring Apr 21, 2026, 08:32 AM UTC

    We are continuing to monitor for any further issues.

  3. resolved Apr 21, 2026, 09:20 AM UTC

    If self hosted customer are still affected, please reach out to our support team.

Read the full incident report →

Major April 17, 2026

Git clone operations failing with VCS agents

Detected by Pingoru
Apr 17, 2026, 01:45 PM UTC
Resolved
Apr 17, 2026, 03:02 PM UTC
Duration
1h 17m
Timeline · 3 updates
  1. 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.

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

  3. resolved Apr 17, 2026, 03:02 PM UTC

    This incident has been resolved.

Read the full incident report →

Major April 14, 2026

Issues resolving correct module configuration when creating a new module version

Detected by Pingoru
Apr 14, 2026, 01:35 PM UTC
Resolved
Apr 14, 2026, 02:23 PM UTC
Duration
48m
Affected: Event processing
Timeline · 4 updates
  1. investigating Apr 14, 2026, 01:35 PM UTC

    We're currently investigating the issue, and will provide an update soon.

  2. identified Apr 14, 2026, 02:04 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Apr 14, 2026, 02:08 PM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Apr 14, 2026, 02:23 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor March 31, 2026

Spacelift Terraform Provider v1.47.0 incorrect signature

Detected by Pingoru
Mar 31, 2026, 02:28 PM UTC
Resolved
Mar 31, 2026, 02:45 PM UTC
Duration
17m
Timeline · 5 updates
  1. 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.

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

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

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

  5. resolved Mar 31, 2026, 02:45 PM UTC

    We have confirmed the correct functionality of v1.47.1

Read the full incident report →

Major March 16, 2026

Environment disruptions (app.us.spacelift.io)

Detected by Pingoru
Mar 16, 2026, 04:24 PM UTC
Resolved
Mar 16, 2026, 08:03 PM UTC
Duration
3h 39m
Timeline · 4 updates
  1. 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.

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

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

  4. resolved Mar 16, 2026, 08:03 PM UTC

    The issue has been resolved

Read the full incident report →

Minor March 2, 2026

Trivy plugin failing with 404 error

Detected by Pingoru
Mar 02, 2026, 12:59 PM UTC
Resolved
Mar 02, 2026, 02:03 PM UTC
Duration
1h 4m
Timeline · 3 updates
  1. 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.

  2. resolved Mar 02, 2026, 02:03 PM UTC

    This incident has been resolved. See the postmortem for resolution instructions.

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

Read the full incident report →

Looking to track Spacelift downtime and outages?

Pingoru polls Spacelift's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Spacelift reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Spacelift alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Spacelift for free

5 free monitors · No credit card required