Spacelift Outage History

Spacelift is up right now

Spacelift had 23 outages in the last 2 years totaling 45h 45m of downtime — averaging 0.9 incidents per month.

There were 23 Spacelift outages since June 7, 2024 totaling 45h 45m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://spacelift.statuspage.io

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 →

Major November 18, 2025

Elevated GitHub Error Rate

Detected by Pingoru
Nov 18, 2025, 09:21 PM UTC
Resolved
Nov 18, 2025, 10:10 PM UTC
Duration
48m
Affected: HTTP APIAPI Errors
Timeline · 2 updates
  1. 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.

  2. resolved Nov 18, 2025, 10:10 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 30, 2025

Event Processing Delays

Detected by Pingoru
Oct 30, 2025, 08:30 PM UTC
Resolved
Oct 30, 2025, 09:25 PM UTC
Duration
55m
Affected: Event processingWebhooks
Timeline · 4 updates
  1. investigating Oct 30, 2025, 08:30 PM UTC

    We're seeing increased delays and/or elevated error rates in our event processing queue.

  2. identified Oct 30, 2025, 08:53 PM UTC

    The root cause was asynchronous processing being throttled

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

  4. resolved Oct 30, 2025, 09:25 PM UTC

    We think the impact from the issue is over.

Read the full incident report →

Major October 17, 2025

Elevated API Errors

Detected by Pingoru
Oct 17, 2025, 09:36 AM UTC
Resolved
Oct 17, 2025, 09:47 AM UTC
Duration
11m
Affected: GraphQL APIEvent processingPlatform UI
Timeline · 2 updates
  1. 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.

  2. resolved Oct 17, 2025, 10:05 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical August 7, 2025

Spacelift unavailable

Detected by Pingoru
Aug 07, 2025, 01:23 PM UTC
Resolved
Aug 07, 2025, 01:31 PM UTC
Duration
8m
Affected: GraphQL APIEvent processing
Timeline · 2 updates
  1. 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.

  2. resolved Aug 07, 2025, 01:31 PM UTC

    We have successfully resolved the deployment issue and Spacelift is available again.

Read the full incident report →

Major July 23, 2025

Incident affecting run scheduling

Detected by Pingoru
Jul 23, 2025, 08:39 AM UTC
Resolved
Jul 23, 2025, 10:16 AM UTC
Duration
1h 37m
Affected: Event processingPublic workers
Timeline · 4 updates
  1. 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.

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

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

  4. resolved Jul 23, 2025, 10:16 AM UTC

    After continuing to monitor the system we have confirmed that it is stable again.

Read the full incident report →

Notice June 27, 2025

Invalid CANCELED Value in Stack List

Detected by Pingoru
Jun 27, 2025, 12:46 PM UTC
Resolved
Jun 27, 2025, 02:13 PM UTC
Duration
1h 27m
Timeline · 3 updates
  1. 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.

  2. monitoring Jun 27, 2025, 01:58 PM UTC

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

  3. resolved Jun 27, 2025, 02:13 PM UTC

    This incident has been resolved.

Read the full incident report →

Major May 27, 2025

Spacelift GraphQL API unavailable

Detected by Pingoru
May 27, 2025, 09:18 AM UTC
Resolved
May 27, 2025, 10:05 AM UTC
Duration
46m
Affected: GraphQL API
Timeline · 3 updates
  1. 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.

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

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

Read the full incident report →

Minor April 10, 2025

Slow database queries

Detected by Pingoru
Apr 10, 2025, 04:37 AM UTC
Resolved
Apr 10, 2025, 05:56 AM UTC
Duration
1h 18m
Affected: GraphQL APIEvent processing
Timeline · 4 updates
  1. investigating Apr 10, 2025, 04:37 AM UTC

    We are experiencing degradation in our database response times.

  2. identified Apr 10, 2025, 04:54 AM UTC

    We've identified the core issue and currently are solving it.

  3. monitoring Apr 10, 2025, 05:26 AM UTC

    A fix has been rolled out and we're monitoring the results.

  4. resolved Apr 10, 2025, 05:56 AM UTC

    The incident has been resolved.

Read the full incident report →

Major April 8, 2025

Difficulties for users to log in

Detected by Pingoru
Apr 08, 2025, 10:17 AM UTC
Resolved
Apr 08, 2025, 11:39 AM UTC
Duration
1h 21m
Affected: Platform UI
Timeline · 3 updates
  1. identified Apr 08, 2025, 10:17 AM UTC

    We're currently investigating an issue that may be preventing some users from logging in. Our team is actively working to resolve this as quickly as possible. We appreciate your patience and will provide updates as soon as we have more information.

  2. monitoring Apr 08, 2025, 10:25 AM UTC

    We have released a fix and are seeing successful logins.

  3. resolved Apr 08, 2025, 11:39 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice February 14, 2025

Reenabled ignored run warnings

Detected by Pingoru
Feb 14, 2025, 12:57 PM UTC
Resolved
Feb 10, 2025, 11:00 AM UTC
Duration
Timeline · 1 update
  1. resolved Feb 14, 2025, 12:57 PM UTC

    The ignored run warnings feature has been reenabled following the resolution of the previous incident, "Degraded performance related to ignored run warnings."

Read the full incident report →

Minor February 6, 2025

Degraded performance related to ignored run warnings

Detected by Pingoru
Feb 06, 2025, 10:41 AM UTC
Resolved
Feb 06, 2025, 02:39 PM UTC
Duration
3h 58m
Affected: GraphQL APIEvent processingPlatform UI
Timeline · 2 updates
  1. monitoring Feb 06, 2025, 10:41 AM UTC

    We have identified an edge-case in the ignored run warnings feature that may impact system performance. While we are investigating and attempting to fix this issue, we have temporarily disabled the feature. While the feature is disabled we will not display information about why runs were not triggered or why stacks are not in sync with the latest commit. We will continue to investigate the situation and will provide an update as soon as we have more information.

  2. resolved Feb 06, 2025, 02:39 PM UTC

    We are continuing to monitor the system performance and have decided to continue to keep the ignored run warnings feature disabled temporarily. We are resolving this incident for now, and will aim to re-enable the feature as soon as possible.

Read the full incident report →

Major November 27, 2024

Partial MFA unavailability

Detected by Pingoru
Nov 27, 2024, 01:25 AM UTC
Resolved
Nov 27, 2024, 03:15 AM UTC
Duration
1h 50m
Timeline · 2 updates
  1. identified Nov 27, 2024, 01:25 AM UTC

    We've identified a regression caused by a recent deployment that results in MFA not working for all types of keys. We've identified the issue and are working on a fix.

  2. resolved Nov 27, 2024, 03:15 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor November 4, 2024

Degraded public worker availability

Detected by Pingoru
Nov 04, 2024, 12:57 AM UTC
Resolved
Nov 04, 2024, 01:47 AM UTC
Duration
49m
Affected: Public workers
Timeline · 3 updates
  1. investigating Nov 04, 2024, 12:57 AM UTC

    We're noticing a degraded availability of workers on the public (shared) worker pool

  2. monitoring Nov 04, 2024, 01:47 AM UTC

    Spacelift runs were failing while attempting to verify the Spacelift worker binary. The problem was caused by an expired GPG public key. The GPG key has now been updated and runs are succeeding again.

  3. resolved Nov 04, 2024, 01:47 AM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 30, 2024

Delayed handling of events

Detected by Pingoru
Oct 30, 2024, 03:40 PM UTC
Resolved
Oct 30, 2024, 04:53 PM UTC
Duration
1h 12m
Affected: Event processingPublic workers
Timeline · 4 updates
  1. investigating Oct 30, 2024, 03:40 PM UTC

    We are seeing an increased error rate when handling webhooks for all customers. This is causing a delay in runs being scheduled.

  2. monitoring Oct 30, 2024, 04:13 PM UTC

    We have introduced a quick fix for handling events.

  3. identified Oct 30, 2024, 04:28 PM UTC

    We have identified an issue with our object storage abstraction, we are rolling back to a previous release.

  4. resolved Oct 30, 2024, 04:53 PM UTC

    Our monitors are reporting that all events have been processed. The issue has been resolved.

Read the full incident report →

Minor October 28, 2024

GitHub Pull Requests Comments Failing

Detected by Pingoru
Oct 28, 2024, 01:32 PM UTC
Resolved
Oct 28, 2024, 02:04 PM UTC
Duration
31m
Affected: Event processing
Timeline · 3 updates
  1. identified Oct 28, 2024, 01:32 PM UTC

    We have identified an issue with Spacelift creating GitHub Pull Request notifications. We are working on a fix for this now and will provide more information soon. In the meantime some Pull Requests may not receive comments from Spacelift.

  2. identified Oct 28, 2024, 01:33 PM UTC

    We are continuing to work on a fix for this issue.

  3. resolved Oct 28, 2024, 02:04 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 11, 2024

Read and write users are unable to view tracked runs

Detected by Pingoru
Oct 11, 2024, 11:23 AM UTC
Resolved
Oct 11, 2024, 11:29 AM UTC
Duration
6m
Affected: Platform UI
Timeline · 3 updates
  1. investigating Oct 11, 2024, 11:23 AM UTC

    We have identified the issue and are in the process of deploying the fix.

  2. identified Oct 11, 2024, 11:23 AM UTC

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

  3. resolved Oct 11, 2024, 11:29 AM UTC

    This incident has been resolved.

Read the full incident report →