Is Tuist down?

Last checked 2m ago
Current status
Tuist is having a partial outage

2 active incidents: [Resolved] Sign ups are broken, [Resolved] Sign ups are broken

Official status page: https://status.tuist.dev · Polled every 5 minutes · 0 components tracked

Tuist is reporting a partial outage right now (last checked 2m 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 30 incidents in the last 90 days (78.89% uptime). Get email, Slack, Discord, or webhook alerts the moment Tuist reports a new incident — free for 5 monitors, no credit card.

Users who monitor Tuist also follow these DevOps services: GitHub Confluence Circle CI OpsGenie JFrog Papertrail Airbrake Splunk OnCall Datadog EU RubyGems View all 6,000+ providers
Tuist uptime 78.89% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incidents 2

  1. Ongoing ● 10d 8h
    Started Sep 03, 2026, 09:06 PM UTC
    Timeline · 1 update
    • 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.

    Latest: Our bot protection prohibited real users to sign up. We'll add a postmortem tomorrow to prevent this from happening in the future.

  2. Ongoing ● 10d 8h
    Started Sep 03, 2026, 08:46 PM UTC
    Timeline · 1 update
    • investigating · Sep 03, 2026, 08:46 PM UTC

      Sign ups are currently broken

    Latest: Sign ups are currently broken

Recent outages & incidents

Past 90 days
  1. Resolved 14d
    Started Aug 13, 2026, 09:16 AM UTC · Resolved Aug 27, 2026, 09:17 AM UTC
    Timeline · 1 update
    • 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.

    Latest: 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…

  2. Resolved 14d 16h
    Started Aug 12, 2026, 04:44 PM UTC · Resolved Aug 27, 2026, 09:17 AM UTC
    Timeline · 1 update
    • investigating · Aug 12, 2026, 04:44 PM UTC

      All processors are back online and the tests are now being processed again, however, it will take some time to clear up the whole clogged up queue.

    Latest: All processors are back online and the tests are now being processed again, however, it will take some time to clear up the whole clogged up queue.

  3. Resolved 14d 18h
    Started Aug 12, 2026, 02:53 PM UTC · Resolved Aug 27, 2026, 09:17 AM UTC
    Timeline · 1 update
    • investigating · Aug 12, 2026, 02:53 PM UTC

      No tests are currently being processed due to all processors being down

    Latest: No tests are currently being processed due to all processors being down

  4. Resolved 14d
    Started Aug 04, 2026, 06:07 AM UTC · Resolved Aug 18, 2026, 06:11 AM UTC
    Timeline · 1 update
    • 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.

    Latest: 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, …

  5. Resolved 14d
    Started Aug 04, 2026, 06:01 AM UTC · Resolved Aug 18, 2026, 06:11 AM UTC
    Timeline · 1 update
    • 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.

    Latest: 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, cach…

See the full Tuist outage history

25 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

Outage history

Past 90 days · 30 incidents View full outage history →