Search

Companies / Dagster / incidents

Dagster: Dagster UI down for multiple users

Impact: majorStatus: postmortemStarted Resolved (38 min)6 updatesSource: stspg.io (opens in new tab)
Summary

Dagster reported a major Dagster Cloud UI outage affecting multiple users, starting 2025-02-27 10:52 UTC and resolved at 2025-02-27 11:29 UTC (37 min). A compute log download fault caused web-server timeouts; a fix restored access, while STDOUT/STDERR tabs remained temporarily disabled before later restoration. Agents, runs, and automations were unaffected.

Machine-written from the archived incident (Sol). Check the timeline before relying on it.

Affected components: Dagster Cloud UI

Timeline of updates

  1. investigating

    We've received reports from multiple users having trouble accessing the Dagster Cloud UI. Our engineering team is currently investigating.

  2. investigating

    We are continuing to investigate this issue.

  3. investigating

    We have rolled out a fix and are monitoring service restoration. The Dagster+ UI is available again. STDERR and STDOUT tabs on runs are temporarily disabled.

  4. monitoring

    We have rolled out a fix and are monitoring service restoration. The Dagster+ UI is available again. STDERR and STDOUT tabs on runs are temporarily disabled.

  5. resolved

    The Dagster+ UI is restored. Agents, runs, and automations are not affected. We will continue to work to restore STDOUT and STDERR in the UI during US business hours. In the meantime, compute logs will continue to upload but will not be accessible via the UI. [UPDATE 1:10 pm EST] STDERR and STDOUT are available again in the UI for all users.

  6. postmortem

    In addition to [structured event logs](https://docs.dagster.io/guides/monitor/logging/#structured-event-logs) that appear in the Dagster UI, Dagster supports [raw compute logs](https://docs.dagster.io/guides/monitor/logging/#raw-compute-logs) to capture STDERR and STDOUT. During the affected window, a fault in our compute log download process resulted in timeouts and diminished responsiveness of our web servers. We mitigated the issue by temporarily disabling compute log downloads before adjusting compute log behavior so that the conditions that led to the failure are no longer possible. Log functionality has since been fully restored. We've also adjusted our incident process to ensure status pages are posted more quickly in the future. Please reach out if you have additional questions. Thank you for your patience.

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Dagster profile · Recent Dagster incidents · Markdown · JSON