- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 29of 100
What to do
Check whether your product depends on Spacelift. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 50m it lasted.
Anything that failed between 2024-11-27 01:25 UTC and 2024-11-27 03:15 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.
Root cause
We've identified a regression caused by a recent deployment that results in MFA not working for all types of keys.
Category: Deploy or config change
Read the postmortemUpdates from Spacelift 2
- identified
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.
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-a4a6e62cb6
Is Spacelift still down?
No, this incident was resolved 2024-11-27 03:15 UTC. For Spacelift's live state, see https://down.guide/providers/spacelift.
How long did it last?
1h 50m, from 2024-11-27 01:25 UTC to 2024-11-27 03:15 UTC, by the times Spacelift posted.
What caused it?
Deploy or config change. Spacelift wrote: "We've identified a regression caused by a recent deployment that results in MFA not working for all types of keys." The postmortem: https://stspg.io/4521t6bjq2qh
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.