Changes Dagster Elevated errors in launching serverless runs

Dagster: Major incident: Elevated errors in launching serverless runs

Major incidentoutage (model (Jev), 100%)Changed 2026-11-06 23:12 UTCDetected 2026-11-06 23:13 UTCdagstercloud.statuspage.io

Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

~~Struck in red~~ is what Dagster removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1

not present

Elevated errors in launching serverless runs

AddedImpact#2

not present

major

AddedStatus#3

not present

monitoring

AddedStart time#4

not present

2026-11-06 23:12 UTC

AddedAffected components#5

not present

API

AddedUpdatemonitoring2026-11-06 23:12 UTC#6

not present

An upstream issue in AWS is causing errors in Dagster+, which is preventing Dagster+ Serverless runs from properly starting. We are monitoring AWS status. Dagster+ Serverless uses ECS in us-west-2. You can track AWS status in resolving this issue here: https://health.aws.amazon.com/health/status

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

Nov 6
After captured 23:13 UTC
In the 2026-11-06 checkpoint, timestamped by FreeTSA and DigiCert on Nov 7, 00:44 UTC. Record hash df1e94e865e59497…
Download proof

History of this incident

TodaySaturday, November 7Sat, Nov 7

2 rewrites, 1 incident change

Normal progress
01:34Incident
Incident updateElevated errors in launching serverless runs
Normal progress
01:04Edited by the vendor
Elevated errors in launching serverless runs
Dagster edited its 11-06 23:12 UTC monitoring update to say AWS had resolved the immediate regression that prevented Dagster+ Serverless runs from properly starting. Dagster continued monitoring pending official AWS resolution; the update identifies ECS in us-west-2 as the affected dependency.
Normal progress
00:34Edited by the vendor
Elevated errors in launching serverless runs
Dagster edited its 11-06 23:12 UTC monitoring update to say AWS had identified the upstream issue and was working on a resolution. The issue prevented Dagster+ Serverless runs from starting properly; the service uses ECS in us-west-2. The edit provided no impact level, start time, duration or confirmed fix.

YesterdayFriday, November 6Fri, Nov 6

1 incident change

Outage
23:12Major incident
Elevated errors in launching serverless runsthis change

Cite this

Major incident: Elevated errors in launching serverless runs on Dagster’s status page, changed 2026-11-06 23:12 UTC (change 1 of 4).

Title: Major incident: Elevated errors in launching serverless runs
Vendor: Dagster
Date: 2026-11-06 23:12 UTC
URL: https://rewindex.com/change/i241f2e7f1cda0d

All Dagster changes Dagster profile Markdown JSON