Dagster: Continued monitoring of Degraded performance in Dagster+
Affected components: Dagster Cloud UI
Timeline of updates
- monitoring
We're continuing to monitor the archival process from the previous incident. While it is making progress, it's taking longer than we hoped. We'll continue to monitor and have identified areas where we can speed up recovery. Large customers may see degraded performance in the UI but we expect this to improve as the process recovers.
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.
First version captured
In the 2026-10-30 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
b26fc64093052a16…
Impact, status and times are the vendor’s own, as last archived. View on dagstercloud.statuspage.io (opens in new tab).