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.

We are reviewing all packages that are missing or have inconsistent checksums with the saved values and fixing them.

Some Swift packages that used to be present in the registry are returned as absent.

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.

Some users reported that packages previously resolved through the registry started being resolved as not found.

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

We restored the service and are monitoring the situation.

Tuist's main service available through tuist.dev is currently unavailable

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.

The deployment of the fix is happening.

We've identified the reason and put together a fix.

The processing of build and test results is getting stuck