- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 19of 100
What to do
Check whether your product depends on Spacelift. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 6m it lasted.
Anything that failed between 2026-07-29 13:39 UTC and 2026-07-29 15:44 UTC may need a replay.Subscribe to Spacelift's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=spacelift works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Spacelift 3
- investigating
We are experiencing failing AWS API calls for runs using hashicorp/aws provider with version v6.57.0.
provider
- identified
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
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f1fc1bbdb2
Is Spacelift still down?
No, this incident was resolved 2026-07-29 15:44 UTC. For Spacelift's live state, see https://down.guide/spacelift.
How long did it last?
2h 6m, from 2026-07-29 13:39 UTC to 2026-07-29 15:44 UTC, by the times Spacelift posted.
What caused it?
Spacelift hasn't published a root cause. If it does, it shows here.
Where does this come from?
Spacelift's official status page, https://spacelift.statuspage.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.