Skip to main content
Spacelift

Issues resolving correct module configuration when creating a new module version

Partial outage Lasted 48m · started · Spacelift's page

Level
confirmed
Worst impact
Partial outage
Components
Event processing
Down Index
28of 100

What to do

  • Check whether you use Spacelift Event processing. 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 48m it lasted.

    Anything that failed between 2026-04-14 13:35 UTC and 2026-04-14 14:23 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 4

  1. investigating

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

    provider

  2. identified

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

    provider

  3. monitoring

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

    provider

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

Is Spacelift still down?

No, this incident was resolved 2026-04-14 14:23 UTC. For Spacelift's live state, see https://down.guide/spacelift.

How long did it last?

48m, from 2026-04-14 13:35 UTC to 2026-04-14 14:23 UTC, by the times Spacelift posted.

What was affected?

Spacelift named Event processing.

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.