Is Dagster Down?
Reachable from all 8 checked regions
Average response time: 164ms
Last checked · checks run every 6 hours
Official status page: https://dagstercloud.statuspage.io
Dagster uptime
Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 27 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.
30-day history
27-day clean streakReachability by region
Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.
What Dagster does
Dagster is a data orchestration platform for building and scheduling data pipelines in Python. In a Dagster+ Hybrid deployment the orchestration control plane is hosted by Dagster while pipeline code runs inside containers in the customer's own environment, managed by an agent they operate on Kubernetes, AWS ECS, Docker or Azure. Data teams use it to schedule pipelines and to see what failed.
What an outage looks like
The Dagster Cloud interface will not load run history or asset graphs, so there is no view of what is running. Scheduled runs may not be launched, because the schedule lives in the hosted control plane rather than on the agent. Runs that do execute stop reporting status and logs, leaving them shown as in progress. The API returns errors to any tooling built on it.
What to do about it
Check dagstercloud.statuspage.io, which reports just two components: API and Dagster Cloud UI. If only the UI is affected, the missing thing is the view of the work rather than the work itself. Your agent and your pipeline code run in your own environment, so restarting the agent during a control-plane incident is not a fix and can interrupt containers that were still doing useful work.
Is it down for everyone, or just you?
If this page says Dagster is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.
Related services
Dagster outage FAQ
Does a Dagster Cloud outage stop pipelines running on my own infrastructure?
Why is my run still shown as in progress?
What do the two components on the status page mean?
Should I restart my agent during an incident?
How we measure this
- We request Dagster's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
- A region counts as down only when it gets no usable HTTP response. A
403or429means the origin answered and refused us, which we report as blocked, never as an outage. - A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
- Response times average only the regions that actually served the page, so a timeout never inflates the number.
- Where Dagster publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.
Get alerted when Dagster goes down
This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.
Start Free Monitoring