Tuist experienced a major incident on July 28, 2026, lasting 14d. The incident has been resolved; the full update timeline is below.
Update timeline
- 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.