Is Tuist down?
Last checked 3m ago18 active incidents: [Resolved] Missing Swift registry packages, [Resolved] Missing Swift registry packages · +16 more
Tuist is reporting a partial outage right now (last checked 3m ago). Some components are affected; others remain operational.
Real-time Tuist status, recent outages, and incident history — pulled directly from Tuist's official status page at https://status.tuist.dev every 5 minutes. Pingoru tracks 0 Tuist services and has captured 22 incidents in the last 90 days (86.67% uptime). Get email, Slack, Discord, or webhook alerts the moment Tuist reports a new incident — free for 5 monitors, no credit card.
Active incidents 18
-
Timeline · 1 update
- investigating · Jul 28, 2026, 05:21 PM UTC
A failed deployment left legacy registry synchronizers writing alongside the new registry, while regional object-storage replicas sometimes returned older archive bytes. This caused missing versions, checksum mismatches, and signature failures. We paused legacy registry syncing without affecting cache availability, repaired and audited the package metadata and archives, and confirmed zero remaining metadata checksum mismatches. Production is protected by the live fix, and pull request #12120 makes authoritative archive reads durable across future deployments.
Latest: A failed deployment left legacy registry synchronizers writing alongside the new registry, while regional object-storage replicas sometimes returned older archive bytes. This cause…
-
-
Timeline · 1 update
- investigating · Jul 28, 2026, 03:23 PM UTC
We are reviewing all packages that are missing or have inconsistent checksums with the saved values and fixing them.
Latest: We are reviewing all packages that are missing or have inconsistent checksums with the saved values and fixing them.
-
-
Timeline · 1 update
- investigating · Jul 28, 2026, 01:00 PM UTC
Some Swift packages that used to be present in the registry are returned as absent.
Latest: Some Swift packages that used to be present in the registry are returned as absent.
-
-
Timeline · 1 update
- investigating · Jul 27, 2026, 01:11 PM UTC
The package syncing had a bug that prevented some versions from persisting. We've fixed the bug and deployed it, forcing the resync of the packages reported by users.
Latest: The package syncing had a bug that prevented some versions from persisting. We've fixed the bug and deployed it, forcing the resync of the packages reported by users.
-
-
Timeline · 1 update
- investigating · Jul 27, 2026, 01:01 PM UTC
Some users reported that packages previously resolved through the registry started being resolved as not found.
Latest: Some users reported that packages previously resolved through the registry started being resolved as not found.
-
+13 more ongoing incidents — sign up free to track them all.
Recent outages & incidents
Past 90 days-
Timeline · 1 update
- investigating · Jun 14, 2026, 01:59 PM UTC
Production tuist.dev returned 503 because all main server pods were crash-looping during startup. The immediate failure was a timeout in license validation against Keygen, but Keygen itself was healthy. The real issue was the production stable egress gateway. Server pod traffic is routed through a Cilium egress gateway using the fixed IP 116.202.0.10. After node churn, the gateway node label and Hetzner floating IP were not attached to any active node, so selected server traffic could not reach the public internet. We restored service by assigning the floating IP to a live general worker, labeling that node as the stable egress gateway, forcing Cilium to refresh the policy, and restarting the server deployment. tuist.dev is now healthy again. To prevent this from recurring, we are working on making the stable egress setup declarative/self-healing instead of relying on a manual node handoff, and adding monitoring for the gateway readiness and server egress path.
Latest: Production tuist.dev returned 503 because all main server pods were crash-looping during startup. The immediate failure was a timeout in license validation against Keygen, but Keyg…
-
-
Timeline · 1 update
- investigating · Jun 12, 2026, 08:41 AM UTC
Some of our caching nodes exhibited intermittent failures under high load, which we've mitigated by adding additional regional nodes. We are actively working on developing and testing a new solution that we plan to deploy in a per-tenant model fashion that will self-regulate under high-load scenarios.
Latest: Some of our caching nodes exhibited intermittent failures under high load, which we've mitigated by adding additional regional nodes. We are actively working on developing and test…
-
-
Timeline · 1 update
- investigating · Jun 08, 2026, 12:37 PM UTC
All stuck test results have been processed now. We're putting up an alert to catch a condition like this sooner.
Latest: All stuck test results have been processed now. We're putting up an alert to catch a condition like this sooner.
-
- Tuist
Timeline · 2 updates
- investigating · May 04, 2026, 04:53 PM UTC
Status: Investigating The test results are stuck in "in processing". We're working on resolving the issue. The rest of the features, like build insights, are not impacted. Affected components Tuist (Operational)
- resolved · May 04, 2026, 05:18 PM UTC
Status: Resolved The test results are now being processed again. We're putting the following mitigations in place, so this doesn't happen again and the issue is resolved faster: - We will be adding a redundant Mac machine for processing the xcresults remotely - We're adding additional monitoring to ensure each new release is healthy. Affected components Tuist (Operational)
Latest: Status: Resolved The test results are now being processed again. We're putting the following mitigations in place, so this doesn't happen again and the issue is resolved faster: - …
-
See the full Tuist outage history
18 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Tuist outage history →Or sign up free to get alerts when Tuist breaks · 10 free monitors · No credit card
- Started Jul 28, 2026, 05:21 PM UTC · ● 2d 16h
- Started Jul 28, 2026, 03:23 PM UTC · ● 2d 17h
- Started Jul 28, 2026, 01:00 PM UTC · ● 2d 20h
- Started Jul 27, 2026, 01:11 PM UTC · ● 3d 20h
- Started Jul 27, 2026, 01:01 PM UTC · ● 3d 20h
- Started Jul 26, 2026, 08:45 AM UTC · ● 5d
- Started Jul 26, 2026, 08:27 AM UTC · ● 5d
- Started Jul 26, 2026, 08:19 AM UTC · ● 5d 1h