Tuist Outage History
Tuist is up right nowPingoru has recorded 47 incidents for Tuist: 47 in the last 12 months and 28 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 0 of 720 (0%) |
| May 2026 | 1 | 0 of 744 (0%) |
| June 2026 | 3 | 481 of 720 (67%) |
| July 2026 | 18 | 345 of 744 (46%) |
| August 2026 | 10 | 633 of 744 (85%) |
| September 2026 | 7 | 336 of 720 (47%) |
| October 2026 | 3 | 0 of 528 (0%) |
Incidents, newest first
Major October 4, 2026 [Resolved] Test result uploads failed –
Started Oct 04, 2026, 07:00 PM UTC· resolved Oct 04, 2026, 07:00 PM UTC
- investigating Oct 04, 2026, 07:00 PM UTC
The permanent fix is now live in production. Test result uploads have been working since 18:03 UTC, and the underlying cause is fixed.
Major September 29, 2026 [Resolved] Degraded API performance, cache errors and login failures –
Started Sep 29, 2026, 09:21 PM UTC· resolved Sep 29, 2026, 09:21 PM UTC
- investigating Sep 29, 2026, 09:21 PM UTC
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.
Major September 22, 2026 [Resolved] EU East Unavailable –
Started Sep 22, 2026, 07:22 PM UTC· resolved Sep 22, 2026, 07:22 PM UTC
- investigating Sep 22, 2026, 07:22 PM UTC
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.
Major September 3, 2026 [Resolved] Sign ups are broken 14d
Started Sep 03, 2026, 09:06 PM UTC· resolved Sep 17, 2026, 09:13 PM UTC
- investigating Sep 03, 2026, 09:06 PM UTC
Our bot protection prohibited real users to sign up. We'll add a postmortem tomorrow to prevent this from happening in the future.
Major August 13, 2026 [Resolved] Tests are stuck in processing 14d
Started Aug 13, 2026, 09:16 AM UTC· resolved Aug 27, 2026, 09:17 AM UTC
- investigating Aug 13, 2026, 09:16 AM UTC
The processor got disconnected and we were not alerted immediately after that happened, which lead to tests being stuck in the processing queue. We've identified the root cause and ensuring this doesn't happen again in the future.
Major August 4, 2026 [Resolved] Registry: Users are experiencing failures when installing some packages 14d
Started Aug 04, 2026, 06:07 AM UTC· resolved Aug 18, 2026, 06:11 AM UTC
- investigating Aug 04, 2026, 06:07 AM UTC
After monitoring the registry, we observed no further issues. It is important to note that, because some packages were rebuilt, users will need to clear their cached fingerprints, as those packages now have new checksums. We will publish a detailed RCA next week with more information about the incident and its root cause.
Major August 4, 2026 [Resolved] Cache: Users are experiencing failure to publish packages in the us-west region 14d
Started Aug 04, 2026, 06:01 AM UTC· resolved Aug 18, 2026, 06:11 AM UTC
- investigating Aug 04, 2026, 06:01 AM UTC
A volume reaching its maximum capacity prevented cache resolution, triggering a cascade of failures that left the region largely non-operational. Once disk space was restored, cache resolution resumed and the region became operational again.
Major July 28, 2026 [Resolved] Missing Swift registry packages 14d
Started Jul 28, 2026, 05:21 PM UTC· resolved Aug 11, 2026, 05:24 PM UTC
- 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.
Major July 27, 2026 [Resolved] Packages missing in the Swift registry 14d
Started Jul 27, 2026, 01:11 PM UTC· resolved Aug 10, 2026, 01:20 PM UTC
- 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.
Major July 26, 2026 [Resolved] Service temporarily unavailable 14d
Started Jul 26, 2026, 08:45 AM UTC· resolved Aug 09, 2026, 08:47 AM UTC
- investigating Jul 26, 2026, 08:45 AM UTC
The incident has been resolved, and we are working on better observability to detect incidents of this nature earlier, as well as some changes in our infrastructure so we can recover fast and reliably from these kinds of issues. We'll share a post morten shortly
Major July 21, 2026 [Resolved] Result processing getting stuck 14d
Started Jul 21, 2026, 05:56 PM UTC· resolved Aug 04, 2026, 06:04 PM UTC
- investigating Jul 21, 2026, 05:56 PM UTC
Turns out the processing demand exceeded the capacity. Test results are being processed, but it just takes longer. We are looking into ways to optimize processing time.
Major July 17, 2026 [Resolved] Authentication issues against the cache 14d
Started Jul 17, 2026, 05:46 PM UTC· resolved Jul 31, 2026, 05:50 PM UTC
- investigating Jul 17, 2026, 05:46 PM UTC
A new version of the server has been deployed to ensure users are not blocked from accessing the cache.
Major June 14, 2026 [Resolved] tuist.dev not reachable 14d
Started Jun 14, 2026, 01:59 PM UTC· resolved Jun 28, 2026, 02:00 PM UTC
- 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.
Major June 12, 2026 [Resolved] Intermitent failures interacting with the cache 14d
Started Jun 12, 2026, 08:41 AM UTC· resolved Jun 26, 2026, 08:46 AM UTC
- 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.
Major June 8, 2026 [Resolved] Tests stuck in processing 14d
Started Jun 08, 2026, 12:37 PM UTC· resolved Jun 22, 2026, 12:43 PM UTC
- 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.
Minor May 4, 2026 Test results are stuck being processed – Tuist
Started May 04, 2026, 05:18 PM UTC· resolved May 04, 2026, 05:18 PM UTC
- investigating May 04, 2026, 04:53 PM UTC
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.
- resolved May 04, 2026, 05:18 PM UTC
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.
Minor April 8, 2026 Cache and registry outage – Tuist
Started Apr 08, 2026, 05:30 PM UTC· resolved Apr 08, 2026, 05:30 PM UTC
- investigating Apr 07, 2026, 04:30 PM UTC
Cache and registry are currently unavailable. The team is investigating.
- resolved Apr 07, 2026, 04:42 PM UTC
The incident has been resolved.
- resolved Apr 08, 2026, 05:30 PM UTC
On April 7, 2026, Tuist experienced an incident that made cache endpoints unavailable globally for approximately 12 minutes, from 16:30 UTC to 16:42 UTC. The full post-mortem is available at https://community.tuist.dev/t/post-mortem-cache-and-registry-outage-april-7-2026/966 .
Notice December 5, 2025 Service not available 1h 1m
Started Dec 05, 2025, 09:00 AM UTC· resolved Dec 05, 2025, 10:01 AM UTC
No vendor updates were posted for this incident.
Notice November 18, 2025 Service not reachable 3h 2m
Started Nov 18, 2025, 12:14 PM UTC· resolved Nov 18, 2025, 03:16 PM UTC
No vendor updates were posted for this incident.
Notice October 31, 2025 Degraded service interacting with the cache 5d 23h
Started Oct 31, 2025, 10:01 AM UTC· resolved Nov 06, 2025, 09:44 AM UTC
No vendor updates were posted for this incident.