Third Party Index

Snapshot 26116

Document
Status page
URL
https://status.tuist.dev/
Fetched
HTTP status
200
Content type
text/html; charset=UTF-8
Fetch mode
static
Size
133544 bytes
SHA-256 (raw)
528aea8f961166e782f334575800624a640e622e8dc46c19863e85301d531ccf
SHA-256 (normalized text)
10f9b63cede185355b7e8b9f3a54b5b559fa4219ca1975eecbbd555137b78fbb

Normalized text

Scripts and page chrome removed; this is what change detection compares.

Skip to content
Current status
All systems operational
Operational
API
Public REST and OpenAPI surfaces consumed by the CLI and integrations.
Operational
CLI
Command-line workflows: generate, build, test, cache, registry.
Operational
Cache
Remote build and test cache used by Tuist projects.
Operational
Dashboard
Web dashboard at tuist.dev.
Operational
Documentation
Tuist's documentation site
Operational
Runners
CI runners
Operational
No active incidents.
Sep 29, 2026
Sep 29, 09:21 PM UTC
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.
Sep 29, 09:09 PM UTC
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.
Sep 29, 08:56 PM UTC
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.
Sep 22, 2026
Sep 22, 07:22 PM UTC
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.
Sep 22, 02:45 PM UTC
Resolved.
The EU East cache region is temporarily unavailable