Is Dagster Down?

No — Dagster is up

Dagster's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 171 ms

Right now

The verdict is the worse of these two. How we decide

Dagster's status page

dagstercloud.statuspage.io · read 4 minutes ago · checked every 3 minutes

Operational

Dagster's components, as its status page reports them
Component	Status
API	Operational
Dagster Cloud UI	Operational

Open their status page

FlareWarden checks

dagster.io from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 171 ms
Checked: 5 hours ago

By region

Ashburn reachable, 174 ms
Frankfurt reachable, 235 ms
Johannesburg reachable, 294 ms
London reachable, 65 ms
Los Angeles reachable, 217 ms
Newark reachable, 167 ms
São Paulo reachable, 61 ms
Tokyo reachable, 157 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Ashburn	56 ms	18 ms	17 ms	129 ms
Frankfurt	160 ms	2 ms	10 ms	227 ms
Johannesburg	116 ms	1 ms	75 ms	257 ms
London	13 ms	2 ms	9 ms	49 ms
Los Angeles	139 ms	2 ms	24 ms	204 ms
Newark	94 ms	2 ms	22 ms	158 ms
São Paulo	13 ms	2 ms	7 ms	40 ms
Tokyo	121 ms	1 ms	7 ms	151 ms

We check that dagster.io loads, not every feature behind it. Test it yourself

History

Incidents Dagster reported

Since Oct 22, 15 days · from dagstercloud.statuspage.io

Incidents: 3
Major or critical: 1
Median to resolve: 1d 22h

Continued monitoring of Degraded performance in Dagster+
Unrated · Oct 30
lasted 3d 7h
Degraded performance in Dagster+
minor · Oct 27
lasted 1d 22h
Cloud application cluster outage
critical · Oct 22
lasted 36m

Dagster website availability

Measured by FlareWarden · dagster.io

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 185ms

Last 30 days

73-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of dagster.io from multiple regions every 6 hours. Dagster's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 73 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Dagster outage FAQ

Does a Dagster Cloud outage stop pipelines running on my own infrastructure?

The architecture splits the two. In a Hybrid deployment the control plane is run by Dagster+ while your code executes in containers inside your own environment, managed by your agent. So the compute is yours, but scheduling, coordination and reporting go through the hosted side. Dagster's deployment documentation describes this split without stating what happens to in-flight runs during a control-plane outage.

Why is my run still shown as in progress?

Because status updates travel from your environment to the hosted control plane, and the interface shows the last state it received. If the API component is affected, a run can finish in your infrastructure with the interface never recording that it did. Check your own container logs and any downstream tables before assuming the work did not happen.

What do the two components on the status page mean?

Dagster Cloud reports only API and Dagster Cloud UI. UI is the web interface you read; API is the endpoint your agent, the CLI and any custom tooling talk to. An API incident is the more serious of the two, because it affects the machinery rather than the view of it. A UI-only incident usually means waiting rather than acting.

Should I restart my agent during an incident?

Usually not. The agent runs in your environment and reconnects to the control plane on its own, so restarting it does not fix a hosted-side incident and risks interrupting containers that were still doing useful work. If the agent itself is unhealthy, that is a separate problem from anything the Dagster Cloud status page reports.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Dagster itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Dagster goes down

We check Dagster every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required