Skip to content

Tuist Status
Current status

All systems operational

Operational

Updated Sep 30, 09:09 PM UTC

Components

  1. API
    Public REST and OpenAPI surfaces consumed by the CLI and integrations.
    Operational
  2. CLI
    Command-line workflows: generate, build, test, cache, registry.
    Operational
  3. Cache
    Remote build and test cache used by Tuist projects.
    Operational
  4. Dashboard
    Web dashboard at tuist.dev.
    Operational
  5. Documentation
    Tuist's documentation site
    Operational
  6. Runners
    CI runners
    Operational

Active incidents

No active incidents.

Past 14 days

Incident history
  1. Sep 29, 2026

    Degraded API performance, cache errors and login failures

    Major
    Operational
    1. Resolved.

      We have deployed a permanent fix, and the API, remote cache and login are working normally. The outage was caused by a deployment that changed how API requests are authenticated, which overloaded our servers, and that change has been reverted. If the CLI still reports authentication errors, run tuist auth login again. We apologize for the disruption.

    2. Resolved.

      From 19:50 to 20:35 UTC, a deployment that changed how API requests are authenticated overloaded our servers. API requests slowed down or failed, remote cache requests returned errors, and tuist auth login and session refreshes failed. We rolled the deployment back at 20:30 UTC, and services had recovered by 20:35. A permanent revert is deploying now, and we're monitoring closely. If the CLI still reports authentication errors, run tuist auth login again.

    3. Resolved.

      A faulty deployment caused API slowdowns, cache errors and login failures. We rolled it back and services are recovering, though some authentication requests may still fail for a few more minutes.

  2. Sep 22, 2026

    EU East Unavailable

    Major
    Operational
    1. Resolved.

      This was a traffic instability of the provider's Warsaw region. We're working on with the provider to figure out what went wrong and how we can ensure this doesn't happen in the future.

    2. Resolved.

      The EU East cache region is temporarily unavailable