Dagster Outage History
Dagster is up right nowPingoru has recorded 51 incidents for Dagster: 7 in the last 12 months and 4 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 1 | 1 of 720 (0%) |
| May 2026 | 0 | 0 of 744 (0%) |
| June 2026 | 0 | 0 of 720 (0%) |
| July 2026 | 0 | 0 of 744 (0%) |
| August 2026 | 1 | 1 of 744 (0%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 3 | 52 of 552 (10%) |
Incidents, newest first
Critical October 22, 2026 Cloud application cluster outage 36m API, Dagster Cloud UI
Started Oct 22, 2026, 05:14 PM UTC· resolved Oct 22, 2026, 05:51 PM UTC
- investigating Oct 22, 2026, 05:14 PM UTC
We are experiencing an issue with our production application cluster, impacting all Dagster+ cloud customers. We are currently investigating and working on a resolution.
- investigating Oct 22, 2026, 05:39 PM UTC
We've identified the core issue, and are actively working to remediate. We are rolling back our deploy, and increasing the size of our database cluster to manage the increased load.
- investigating Oct 22, 2026, 05:50 PM UTC
The rollback and upgraded database have completed and the system is operational.
- resolved Oct 22, 2026, 05:51 PM UTC
This incident has been resolved.
Major October 22, 2026 Degraded sensor and schedule evaluations 7h 24m
Started Oct 22, 2026, 01:00 PM UTC· resolved Oct 22, 2026, 08:24 PM UTC
- resolved Oct 22, 2026, 08:52 PM UTC
Between 1:00pm and 1:24pm PT (20:00–20:24 UTC), Dagster+ had trouble communicating with agents. During this window, some sensor and schedule evaluations failed or timed out, and some runs may have started late. Service has recovered. Sensors and schedules are evaluating normally, and failed ticks will resume on their next evaluation. We're monitoring and investigating the root cause.
Minor October 7, 2026 Degraded agent communication delayed schedules and automations 1d 21h API, Dagster Cloud UI
Started Oct 07, 2026, 08:26 PM UTC· resolved Oct 09, 2026, 05:26 PM UTC
- monitoring Oct 07, 2026, 08:26 PM UTC
Between 3:15 PM and 3:45 PM ET (12:15–12:45 PM PT, 19:15–19:45 UTC) on October 7, a backend issue delayed communication between Dagster+ and customer agents. During this window, some schedule, sensor and declarative automation ticks failed with "Unable to reach the user code server" errors, and some code location operations may have been slow or timed out. The issue was resolved by 3:45 PM ET (12:45 PM PT, 19:45 UTC), and ticks have run normally since. Schedule ticks that failed during this window may not have been retried automatically. If you're missing an expected run from that period, you can launch it manually from the Dagster+ UI. We're investigating the root cause and will take steps to prevent it from happening again.
- resolved Oct 09, 2026, 05:26 PM UTC
We've deployed several fixes and performance optimizations that have resolved this issue, and should prevent it in the future.
Minor August 29, 2026 Brief Hybrid Agent Disruption on 2026-08-29 35m
Started Aug 29, 2026, 05:30 PM UTC· resolved Aug 29, 2026, 06:05 PM UTC
- resolved Aug 31, 2026, 06:11 PM UTC
Impact: Dagster+ hybrid agents connecting to the US region via AWS PrivateLink experienced connection loss. Duration: ~30 minutes (17:35 – 18:05 UTC / 13:35 – 14:05 ET on 2026-08-29) Summary: As part of a planned infrastructure migration from our legacy nginx ingress to Istio, we rotated the network load balancers behind our PrivateLink endpoint service. This involved disconnecting the previous set of consumer VPC endpoints so that new connections would route through the Istio-backed path. During the ~30 minute window between endpoint disconnection and full re-establishment, hybrid agents connecting via PrivateLink were unable to reach the Dagster+ control plane and appeared as unhealthy in our health dashboard. Once new endpoints came online, agents automatically reconnected and returned to a healthy state without customer action. What was affected: Hybrid agents connecting to Dagster+ US region via AWS PrivateLink Job runs, code location updates, and metadata operations dependent on that connection were paused (queued locally) until the connection recovered What was NOT affected: The Dagster+ UI and API remained fully available Non-PrivateLink hybrid agents (using public network connectivity) Dagster+ Serverless (EU and US) Dagster+ EU hybrid customers Timeline (EDT): 12:35 — Existing PrivateLink consumer endpoints intentionally disconnected as part of the migration 12:40 – 12:55 — Agents in a disconnected state; new endpoint provisioning in progress 13:00 — Partial reconnection observed (~10% of affected agents) 13:05 — Full recovery to pre-migration baseline Root Cause: Planned migration step: swapping the network load balancers attached to the PrivateLink service. The gap in agent connectivity occurred while new endpoints were being provisioned on our side. The recovery took slightly longer than the pre-migration plan estimated because a subset of new endpoints hit a transient AWS API race condition on creation and required a retry.
- postmortem Aug 31, 2026, 06:15 PM UTC
**What happened** During a planned nginx→Istio migration on 2026-08-29 17:35 UTC, we disconnected existing PrivateLink consumer VPC endpoints as part of the cutover. Hybrid customer agents connecting via PrivateLink lost their connections and needed to reconnect via new endpoints on our side. Full recovery at 18:05 UTC, ~30 min. **What went well** * Migration itself completed cleanly; new endpoints healthy immediately after the retry apply. * Metric-based recovery detection \(`healthy_locations_external.ACTIVE`\) surfaced the impact and the recovery in real time. * No data loss; agents automatically re-attached with no customer action required. **What could have gone better** * We did not proactively communicate to affected customers ahead of the maintenance window. Realistically the class of affected customers is a small, known set \(PrivateLink hybrid\); we could have surfaced a maintenance banner in the product a few days in advance rather than a reactive Pylon blast when the disruption started. * Internal VPCE recreation hit a transient AWS API race \(private-DNS namespace not fully released before recreate\), prolonging the maintenance window.
Minor April 29, 2026 Serverless tasks failing to start 1h 12m API
Started Apr 29, 2026, 06:16 PM UTC· resolved Apr 29, 2026, 07:28 PM UTC
- 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.
- resolved Apr 29, 2026, 07:28 PM UTC
The underlying issue has been resolved.
Notice February 23, 2026 Scheduling runs and sensors delay 1h 15m
Started Feb 23, 2026, 08:15 PM UTC· resolved Feb 23, 2026, 09:30 PM UTC
- 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.
Notice November 18, 2025 Some users seeing an older version of the Dagster+ UI 49m Dagster Cloud UI
Started Nov 18, 2025, 02:04 PM UTC· resolved Nov 18, 2025, 02:53 PM UTC
- 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.
- 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.
Notice July 1, 2025 Elevated API latency 12h
Started Jul 01, 2025, 02:00 AM UTC· resolved Jul 01, 2025, 02:00 PM UTC
- 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.
Notice June 27, 2025 The intermittant issues have been fixed. 1m
Started Jun 27, 2025, 06:56 PM UTC· resolved Jun 27, 2025, 06:58 PM UTC
- 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.
- resolved Jun 27, 2025, 06:58 PM UTC
This issue has now been resolved.
Notice June 12, 2025 Impact of GCP incident 6h 9m
Started Jun 12, 2025, 06:59 PM UTC· resolved Jun 13, 2025, 01:08 AM UTC
- 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.
- resolved Jun 13, 2025, 01:08 AM UTC
This incident has been resolved.
Notice April 24, 2025 Dagster+ UI errors 19m Dagster Cloud UI
Started Apr 24, 2025, 06:11 PM UTC· resolved Apr 24, 2025, 06:31 PM UTC
- investigating Apr 24, 2025, 06:11 PM UTC
We're investigating an uptick in Dagster+ UI errors beginning at 10:40PT.
- monitoring Apr 24, 2025, 06:19 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved Apr 24, 2025, 06:31 PM UTC
This incident has been resolved.
Notice March 27, 2025 Some users cannot access catalog UI 3h 30m Dagster Cloud UI
Started Mar 27, 2025, 10:51 AM UTC· resolved Mar 27, 2025, 02:21 PM UTC
- 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.
- identified Mar 27, 2025, 11:53 AM UTC
Issue was identified and a fix is currently being worked on.
- monitoring Mar 27, 2025, 12:24 PM UTC
A fix was deployed and we are monitoring the situation.
- resolved Mar 27, 2025, 02:21 PM UTC
This incident has been resolved.
Notice March 23, 2025 Some Dagster+ Serverless Runs Failing to Start 45m
Started Mar 23, 2025, 07:30 PM UTC· resolved Mar 23, 2025, 08:15 PM UTC
- 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.
Major February 27, 2025 Dagster UI down for multiple users 2h 2m Dagster Cloud UI
Started Feb 27, 2025, 09:27 AM UTC· resolved Feb 27, 2025, 11:29 AM UTC
- 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.
- investigating Feb 27, 2025, 10:25 AM UTC
We are continuing to investigate this issue.
- 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.
- 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.
- 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.
- 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.
Notice February 14, 2025 Elevated errors in the Dagster+ UI 25m
Started Feb 14, 2025, 03:00 PM UTC· resolved Feb 14, 2025, 03:25 PM UTC
- 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"
Major February 7, 2025 Issues with global op concurrency keys 34m API, Dagster Cloud UI
Started Feb 07, 2025, 03:37 PM UTC· resolved Feb 07, 2025, 04:11 PM UTC
- 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.
- 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.
- resolved Feb 07, 2025, 04:11 PM UTC
This incident has been resolved.
Minor October 24, 2024 Degraded Dagster+ UI performance 1h 9m Dagster Cloud UI
Started Oct 24, 2024, 07:55 PM UTC· resolved Oct 24, 2024, 09:05 PM UTC
- 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.
- identified Oct 24, 2024, 08:12 PM UTC
We've identified the issue and are working on a fix.
- monitoring Oct 24, 2024, 08:58 PM UTC
We have rolled out a fix.
- resolved Oct 24, 2024, 09:05 PM UTC
This incident has been resolved.