rewindex

CompaniesDagsterIncidents

Dagster: Elevated API latency failed runs

No impact listedStatus: resolvedStarted Resolved (-595 min)1 updatestspg.io (opens in new tab)

Timeline of updates

  1. resolved

    Increased latency on our storage engine caused a small number of requests to our API to time out at 10:20 UTC and again at 10:47 UTC. This may have resulted in some runs that were running during this time period to fail. The timeouts have now been resolved and we’re in the process of investigating the root cause of the increased latency.

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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Dagster, started 2024-04-01 20:15 UTC, resolved after -595 min, 1 update(s).

Title
Elevated API latency failed runs
Vendor
Dagster
Date
URL
https://rewindex.com/company/dagster/incidents/9pwy1t4s2gq2

Dagster profileRecent Dagster incidentsAll outages on April 1, 2024Dagster in April 2024MarkdownJSON