Skip to main content
Spacelift

GitHub Pull Requests Comments Failing

Degraded Lasted 31m · started · Spacelift's page

Level
confirmed
Worst impact
Degraded
Components
Event processing
Down Index
17of 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 31m it lasted.

    Anything that failed between 2024-10-28 13:32 UTC and 2024-10-28 14:04 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

  1. identified

    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.

    provider

  2. identified

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

    provider

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

Is Spacelift still down?

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

How long did it last?

31m, from 2024-10-28 13:32 UTC to 2024-10-28 14:04 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.