Stilla Outage History

Stilla is up right now

Pingoru has recorded 5 incidents for Stilla: 4 in the last 12 months and 0 in the last 90 days.

Source: status.stilla.ai

5incidents recorded
4last 12 months
0last 90 days
64 minutestypical duration

Incidents, newest first

Major July 16, 2026 WorkOS incident 1h 52m WorkOS SSO, Sign-in / Sign-up

Started Jul 16, 2026, 08:53 AM UTC· resolved Jul 16, 2026, 10:46 AM UTC

  1. investigating Jul 16, 2026, 08:53 AM UTC

    We are monitoring an upstream issue with WorkOS that is affecting sign in and sign out in Stilla.

  2. investigating Jul 16, 2026, 08:54 AM UTC

    We are continuing to investigate this issue.

  3. monitoring Jul 16, 2026, 10:17 AM UTC

    Upstream provider has implemented a fix and we are seeing recovery on sign in and sign out actions. We will continue to monitor the issue.

  4. resolved Jul 16, 2026, 10:46 AM UTC

    This incident has been resolved.

Read the full incident report →

Major June 3, 2026 Degraded Computer Use platform 49m Computer Use

Started Jun 03, 2026, 01:40 PM UTC· resolved Jun 03, 2026, 02:30 PM UTC

  1. investigating Jun 03, 2026, 01:40 PM UTC

    We're investigating degraded performance and failures in computer task execution. This is caused by an ongoing outage at our upstream compute provider, Modal, whose auth subsystem is currently failing. While this is ongoing, agent runs and other features that depend on computer execution may fail or be delayed. The rest of the app is unaffected. We're monitoring Modal's recovery and will update this incident as the situation changes. No action is needed on your end.

  2. resolved Jun 03, 2026, 02:30 PM UTC

    Computer use is now fully operational.

Read the full incident report →

Minor March 11, 2026 Intermittent LLM provider failures 51m Stilla Web, API

Started Mar 11, 2026, 07:45 PM UTC· resolved Mar 11, 2026, 08:36 PM UTC

  1. investigating Mar 11, 2026, 07:45 PM UTC

    We are observing elevated failure rates with Claude family based LLM operations on Google Vertex

  2. monitoring Mar 11, 2026, 08:16 PM UTC

    Degradation reducing — monitoring We're seeing improvement across affected systems. Degradation is reducing and performance is recovering. We're continuing to monitor and will provide an update once we confirm full resolution.

  3. resolved Mar 11, 2026, 08:36 PM UTC

    Resolved — all systems operational All systems are performing normally. We apologize for any inconvenience caused. No further action is required.

Read the full incident report →

Major March 5, 2026 Stilla not responding to @mentions in Slack channels 44m

Started Mar 05, 2026, 08:13 PM UTC· resolved Mar 05, 2026, 08:58 PM UTC

  1. investigating Mar 05, 2026, 08:13 PM UTC

    @mentioning Stilla in a Slack channel has no effect — Stilla is not responding. We are investigating the cause.

  2. investigating Mar 05, 2026, 08:16 PM UTC

    This has been identified as an upstream incident at Slack. See: https://slack-status.com/2026-03/e63ca9cc0d76539c We are monitoring the Slack incident. Stilla will resume normal behavior once Slack resolves the issue.

  3. resolved Mar 05, 2026, 08:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice May 25, 2025 This is an example incident –

Started May 25, 2025, 02:32 PM UTC· resolved May 25, 2025, 02:32 PM UTC

  1. investigating May 26, 2025, 02:16 PM UTC

    When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.

  2. identified May 26, 2025, 02:16 PM UTC

    As you continue to work through the incident, update your customers frequently.

  3. monitoring May 26, 2025, 02:16 PM UTC

    Let your users know once a fix is in place, and keep communication clear and precise.

  4. resolved May 26, 2025, 02:16 PM UTC

    Empathize with those affected and let them know everything is operating as normal.

Read the full incident report →