Is Spacelift Down?

No — Spacelift is up

Reachable from all 8 checked regions

Average response time: 269ms

Last checked 5 hours ago · checks run every 6 hours

Official status page: https://spacelift.statuspage.io

Spacelift uptime

—

Last 7 days

—

Last 30 days

—

Last 90 days

—

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 2 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

Jul 26 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

fra

185ms

DNS 0ms TCP 1ms TLS 3ms TTFB 180ms

gru

62ms

DNS 0ms TCP 3ms TLS 7ms TTFB 55ms

iad

86ms

DNS 1ms TCP 1ms TLS 5ms TTFB 80ms

jnb

401ms

DNS 0ms TCP 0ms TLS 6ms TTFB 378ms

lax

181ms

DNS 0ms TCP 2ms TLS 13ms TTFB 168ms

lhr

187ms

DNS 0ms TCP 2ms TLS 7ms TTFB 180ms

nrt

279ms

DNS 0ms TCP 1ms TLS 6ms TTFB 273ms

ord

122ms

DNS 0ms TCP 2ms TLS 4ms TTFB 93ms

sin

841ms

DNS 0ms TCP 1ms TLS 4ms TTFB 836ms

What Spacelift does

Spacelift is a managed CI/CD platform for infrastructure as code. It runs plan and apply for Terraform and OpenTofu against your cloud accounts, manages state, and enforces policies and approvals before changes land. Runs execute either on worker pools Spacelift operates or on private workers deployed inside the customer's own AWS, Azure, GCP or Kubernetes infrastructure.

What an outage looks like

Runs queue and never start, or start and never report back, so a deploy sits half-finished with no plan output. Pushes to the connected repository stop triggering anything, because event processing is a separate component from the API. The interface may load while the GraphQL API behind it fails, leaving stacks visible but unmanageable.

What to do about it

Read spacelift.statuspage.io and note which layer is affected: GraphQL API, Event processing, Public workers, Platform UI and Self Hosted are separate rows. The page also tracks the upstreams Spacelift depends on, including GitHub webhooks and several AWS services, so a stalled run may be GitHub's rather than Spacelift's. Avoid re-triggering a run that may already be mid-apply.

Is it down for everyone, or just you?

If this page says Spacelift is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

GitHub

AWS

GitLab

Jenkins

Spacelift outage FAQ

Does my infrastructure go down when Spacelift does?

No. Spacelift is the pipeline that changes infrastructure, not a component of it, so anything already deployed keeps running untouched. What stops is your ability to make changes: plans, applies and drift detection. That distinction matters during an incident, because the urge to bypass the platform and apply by hand is what creates state drift afterwards.

Are private workers affected by a Spacelift outage?

Private workers run in your own infrastructure and connect outbound to Spacelift over MQTT or HTTP long-poll, so the machines themselves stay up. They still need the control plane to hand them work, which means an incident on Spacelift's side stops new runs regardless of where the workers live. The status page lists Public workers separately, so that row does not describe your pool.

Can I see what a run did if the interface is down?

Not always, and this is why Platform UI and the GraphQL API are tracked separately. If only the interface is affected, the API and the CLI may still answer. Spacelift encrypts temporary run state end to end so that only the workers in your own pool can read it, so recovering detail mid-incident depends on the platform rather than on anything you hold.

Should I apply Terraform manually while Spacelift is down?

Only with care. Applying outside the platform bypasses the policies and approvals it enforces, and it changes state that Spacelift is tracking, which shows up as drift once it returns. For an urgent production fix it is sometimes the right call, but plan to reconcile the state deliberately afterwards rather than assuming the next run sorts it out.

How we measure this

We request Spacelift's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Spacelift publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Spacelift goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required