- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Public workers
- Regions
- eu, us
What to do
Check whether you use Spacelift Public workers in eu, us. 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 1h 22m it lasted.
Anything that failed between 2026-10-21 00:03 UTC and 2026-10-21 01:26 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
**Root Cause**Read the postmortem
Updates from Spacelift 5
- investigating
We’re seeing an increased number of errors affecting the worker polling API for customers in our US region. Our team is actively working on mitigation and will share updates as they become available.
provider
- identified
We have the fix implemented and we will release it shortly.
provider
- monitoring
We deployed the fix and monitoring.
provider
- resolved
This incident has been resolved.
provider
- postmortem
**Root Cause** A change in a new launcher version caused it to connect by default to the EU endpoint if the region was not explicitly configured. Workers registered in other regions were then rejected at authentication. This was a human error. Detection was delayed for three reasons: * Our pre-release testing did not cover workers outside the EU region well enough. * Launcher authentication errors usually come from individual customer misconfiguration, so the increase was not flagged as a platform issue. * MQTT disconnections coincided with our planned MQTT-to-polling migration, which made the drop look expected. **Mitigations** * **Immediate:** We rolled back to a working version of the launcher * Before every deployment, we will now boot fresh private workers in other regions and confirm that they connect and complete a run. A failure like this should be caught before a release. * We are improving alerting so that authentication failures across multiple customers are flagged automatically as a potential platform issue. **Conclusion** A broken binary caused launchers without a configured region to target the wrong endpoint. Gaps in regional test coverage and alerting meant we did not catch it before customers did. Additional automated checks are being put in place so that this failure would be detected before release along with improved alerting so that we are notified sooner for issues that make it past our automated checks.
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-4c9b6f4e9a
Is Spacelift still down?
No, this incident was resolved 2026-10-21 01:26 UTC. For Spacelift's live state, see https://down.guide/spacelift.
How long did it last?
1h 22m, from 2026-10-21 00:03 UTC to 2026-10-21 01:26 UTC, by the times Spacelift posted.
What was affected?
Spacelift named Public workers in eu, us.
What caused it?
Spacelift wrote: "**Root Cause**" The postmortem: https://stspg.io/h6k0j0f0s71n
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.