rewindex

ChangesDagsterDegraded performance in Dagster+

Dagster: Incident updated: Degraded performance in Dagster+

Incident updateNormal progress (rule, 100%)Changed dagstercloud.statuspage.io (opens in new tab)
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.

ChangedStatus#1
Before: monitoring
After: resolved
AddedResolved time#2
Before: not present
After: 2026-10-29 17:15 UTC
AddedUpdateresolved#3
Before: not present
After: We have deployed a complete fix to our production instance and confirm that this issue has been resolved.

Compared with the previous archived version of this incident (10 to 30-minute polling). 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 these records existed by then and have not been changed since, by anyone, Rewindex included.

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

History of this incident

Thursday, October 29

1 incident change

Wednesday, October 28

1 incident change

Tuesday, October 27

1 incident change

Cite this

Incident updated: Degraded performance in Dagster+ on Dagster’s status page, changed 2026-10-29 17:23 UTC (change 3 of 3).

Title
Incident updated: Degraded performance in Dagster+
Vendor
Dagster
Date
URL
https://rewindex.com/change/rf3df9f9c23b31e

All Dagster changesDagster profileMarkdownJSON