Dagster Outage History

Dagster is up right now

Dagster had 14 outages in the last 2 years totaling 26h 24m of downtime — averaging 0.6 incidents per month.

There were 14 Dagster outages since October 24, 2024 totaling 26h 24m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://dagstercloud.statuspage.io

Minor April 29, 2026

Serverless tasks failing to start

Detected by Pingoru
Apr 29, 2026, 06:16 PM UTC
Resolved
Apr 29, 2026, 07:28 PM UTC
Duration
1h 12m
Affected: API
Timeline · 2 updates
  1. monitoring Apr 29, 2026, 06:16 PM UTC

    We observed an increase in Dagster+ serverless runs failing to start between 10:50AM and 11:00AM PST. Our cloud provider indicated an incident on their end which we have linked to these issues. Failure rate has since gone back down, we will post more information as we learn more.

  2. resolved Apr 29, 2026, 07:28 PM UTC

    The underlying issue has been resolved.

Read the full incident report →

Notice February 24, 2026

Scheduling runs and sensors delay

Detected by Pingoru
Feb 24, 2026, 12:33 AM UTC
Resolved
Feb 24, 2026, 12:33 AM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 24, 2026, 12:33 AM UTC

    A configuration change caused an delay in scheduling runs and sensors. We identified and fixed the issue. The issue was identified at 12:15pm PST and was resolved at 1:30pm PST.

Read the full incident report →

Notice November 18, 2025

Some users seeing an older version of the Dagster+ UI

Detected by Pingoru
Nov 18, 2025, 02:04 PM UTC
Resolved
Nov 18, 2025, 02:53 PM UTC
Duration
49m
Affected: Dagster Cloud UI
Timeline · 2 updates
  1. investigating Nov 18, 2025, 02:04 PM UTC

    We're investigating an issue where some users are seeing a version of the old Dagster+ UI. We've identified the root cause of the problem and are investigating a fix.

  2. resolved Nov 18, 2025, 02:53 PM UTC

    This issue has now been resolved - all users should now be seeing the new Dagster+ UI again.

Read the full incident report →

Notice July 1, 2025

Elevated API latency

Detected by Pingoru
Jul 01, 2025, 02:00 AM UTC
Resolved
Jul 01, 2025, 02:00 PM UTC
Duration
12h
Timeline · 1 update
  1. resolved Jul 02, 2025, 07:01 PM UTC

    We observed some DNS resolution related API latency and errors from 10:10pm-10:35pm EST. We've identified the issue and have released a fix.

Read the full incident report →

Notice June 27, 2025

The intermittant issues have been fixed.

Detected by Pingoru
Jun 27, 2025, 06:56 PM UTC
Resolved
Jun 27, 2025, 06:58 PM UTC
Duration
1m
Timeline · 2 updates
  1. monitoring Jun 27, 2025, 06:56 PM UTC

    We observed some API latency and errors from 2:15pm-2:45pm EST. We've identified the issue and have released a fix.

  2. resolved Jun 27, 2025, 06:58 PM UTC

    This issue has now been resolved.

Read the full incident report →

Notice June 12, 2025

Impact of GCP incident

Detected by Pingoru
Jun 12, 2025, 06:59 PM UTC
Resolved
Jun 13, 2025, 01:08 AM UTC
Duration
6h 9m
Timeline · 2 updates
  1. monitoring Jun 12, 2025, 06:59 PM UTC

    GCP is reporting degraded status for a number of services: https://status.cloud.google.com Dagster+ is largely unaffected. Users using Google to authenticate to Dagster+ may see issues with sign in and authentication. We'll continue to monitor and update with any other Dagster+ related impact.

  2. resolved Jun 13, 2025, 01:08 AM UTC

    This incident has been resolved.

Read the full incident report →

Notice April 24, 2025

Dagster+ UI errors

Detected by Pingoru
Apr 24, 2025, 06:11 PM UTC
Resolved
Apr 24, 2025, 06:31 PM UTC
Duration
19m
Affected: Dagster Cloud UI
Timeline · 3 updates
  1. investigating Apr 24, 2025, 06:11 PM UTC

    We're investigating an uptick in Dagster+ UI errors beginning at 10:40PT.

  2. monitoring Apr 24, 2025, 06:19 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Apr 24, 2025, 06:31 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 27, 2025

Some users cannot access catalog UI

Detected by Pingoru
Mar 27, 2025, 10:51 AM UTC
Resolved
Mar 27, 2025, 02:21 PM UTC
Duration
3h 30m
Affected: Dagster Cloud UI
Timeline · 4 updates
  1. investigating Mar 27, 2025, 10:51 AM UTC

    We detected errors for some users when accessing the catalog Dagster+ UI. Using incognito mode in the browser solves it. We are currently investigating the problem to provide fast mitigation.

  2. identified Mar 27, 2025, 11:53 AM UTC

    Issue was identified and a fix is currently being worked on.

  3. monitoring Mar 27, 2025, 12:24 PM UTC

    A fix was deployed and we are monitoring the situation.

  4. resolved Mar 27, 2025, 02:21 PM UTC

    This incident has been resolved.

Read the full incident report →

Notice March 23, 2025

Some Dagster+ Serverless Runs Failing to Start

Detected by Pingoru
Mar 23, 2025, 07:30 PM UTC
Resolved
Mar 23, 2025, 07:30 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Mar 23, 2025, 10:50 PM UTC

    Between 11:30 AM PST and 12:15 PM PST on Sunday, March 23rd, some Dagster+ Serverless runs failed to start with a “run worker failed” error. We are working with our cloud provider to investigate the root cause.

Read the full incident report →

Major February 27, 2025

Dagster UI down for multiple users

Detected by Pingoru
Feb 27, 2025, 10:52 AM UTC
Resolved
Feb 27, 2025, 11:29 AM UTC
Duration
37m
Affected: Dagster Cloud UI
Timeline · 6 updates
  1. investigating Feb 27, 2025, 09:27 AM UTC

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

  2. investigating Feb 27, 2025, 10:25 AM UTC

    We are continuing to investigate this issue.

  3. investigating Feb 27, 2025, 10:51 AM UTC

    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 Feb 27, 2025, 10:52 AM UTC

    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 Feb 27, 2025, 11:29 AM UTC

    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 Mar 07, 2025, 09:12 PM UTC

    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.

Read the full incident report →

Notice February 14, 2025

Elevated errors in the Dagster+ UI

Detected by Pingoru
Feb 14, 2025, 03:00 PM UTC
Resolved
Feb 14, 2025, 03:00 PM UTC
Duration
—
Timeline · 1 update
  1. resolved Feb 14, 2025, 03:38 PM UTC

    "Between 7:05AM PST and 7:25AM PST there were elevated errors while accessing the Dagster+ UI. The cause of the errors has been identified and fixed and the problem should now be resolved"

Read the full incident report →

Major February 7, 2025

Issues with global op concurrency keys

Detected by Pingoru
Feb 07, 2025, 03:37 PM UTC
Resolved
Feb 07, 2025, 04:11 PM UTC
Duration
34m
Affected: APIDagster Cloud UI
Timeline · 3 updates
  1. identified Feb 07, 2025, 03:37 PM UTC

    Some runs containing ops tagged with concurrency keys that have not been configured explicitly or with a default limit are getting blocked. Separately, there are some UI issues affecting the concurrency key settings page. We have identified fixes for these and are in the process of rolling them out.

  2. monitoring Feb 07, 2025, 03:56 PM UTC

    The fixes has been rolled out and previously blocked runs appear to be progressing. We are continuing to monitor for any issues. The previous blocked runs should progress with their step execution, but may not reach a terminal state and may need to be manually terminated.

  3. resolved Feb 07, 2025, 04:11 PM UTC

    This incident has been resolved.

Read the full incident report →

Minor October 24, 2024

Degraded Dagster+ UI performance

Detected by Pingoru
Oct 24, 2024, 07:55 PM UTC
Resolved
Oct 24, 2024, 09:05 PM UTC
Duration
1h 9m
Affected: Dagster Cloud UI
Timeline · 4 updates
  1. investigating Oct 24, 2024, 07:55 PM UTC

    Some users are seeing degradations loading the Dagster+ UI. We are investigating and working on a fix.

  2. identified Oct 24, 2024, 08:12 PM UTC

    We've identified the issue and are working on a fix.

  3. monitoring Oct 24, 2024, 08:58 PM UTC

    We have rolled out a fix.

  4. resolved Oct 24, 2024, 09:05 PM UTC

    This incident has been resolved.

Read the full incident report →