Astronomer Outage History

We are currently observing elevated task failures and latency for some deployments running in the AWS us-east-1 region. This is related to an ongoing AWS incident affecting a single Availability Zone (use1-az4), where EC2 and EBS resources have experienced impairments. What to expect: You may see intermittent task failures or retries in your deployments. In most cases, these failures are transient and should self-resolve automatically as AWS continues recovery. What you should do: No immediate action is required. However, if you notice consistent or prolonged failures, please reach out to Astronomer Support, and we’ll help investigate further. We are continuing to monitor the situation closely and will share updates as needed. Refer: https://health.aws.amazon.com/health/status

We are investigating delayed delivery for some time-based alerts. The delay is primarily visible for DAG Timeliness alerts, and may also affect Observe-related SLA, Proactive SLA, and Data Quality monitor alerts. DAG Duration and Task Duration alerts do not appear to be affected at this time.

Attempting to access the dags page in the Airflow UI results in a 403 Forbidden error. This should not be affecting task execution.

We’re investigating an issue affecting Dashboard cost breakdown data. For affected customers, cost breakdown information may appear stale and may not have updated since May 1, 2026. Our team is actively investigating the cause and working to restore current data. We’ll share another update as we have more information.

We are continuing to investigate this issue.

It seems to be only in AWS clusters for now. We have a workaround while we investigate.

We are continuing to investigate this issue.

We have identified an issue with Astro Executor deployments where terminating workers can continue to accept new tasks, which can, in some cases, can cause these tasks to fail.

We are currently investigating an issue causing false positive alerts via Astro Alerts. Our team is actively investigating the issue.

We are currently investigating an issue affecting deployment management operations. Users may experience errors when attempting to perform CRUD operations on deployments. Our engineering team is actively investigating and working to restore normal functionality. We will provide further updates as more information becomes available.

We are continuing to investigate this issue.

Some pods in us-central-1 are experiencing CrashLoopBackoff errors. Because at least some of these errors are affecting the components that control Dag-only deploys, newly scaled up worker pods are being affected in at least some cases. We are actively investigating.

Google has confirmed to Astronomer that this is an issue with GKE in the region. We are following the issue closely.

We are currently investigating an issue affecting Airflow worker autoscaling for some deployments hosted on the Shared Azure Cluster in the US-East2 region. As a result of this issue, worker pods may not scale up as expected in response to workload demand. This can lead to tasks remaining in a queued state longer than usual and, in some cases, failing due to queued timeouts. Our engineering team is actively working to identify the root cause and restore normal autoscaling behaviour. We will provide further updates as more information becomes available. Impact: • Affected deployments may experience delayed task execution. • Worker pods may not scale up from zero or may not scale as expected under load. We will continue to share updates on this page as we make progress toward resolution.

We are still in the process of performing critical maintenance on the Astro control plane. Due to upstream dependencies by our cloud providers our changes have taken longer than anticipated. We are actively working to resolve this as quickly as possible and expect to conclude by 20:00 UTC. As a reminder: Your DAGs and tasks will continue to run normally but you may not be able to view them in the UI during the maintenance. DAGs that use the Astro API (such as cross-deployment DAG triggering) will be impacted until this work is complete.

We are currently investigating this issue.

We are currently investigating this issue.

Observability processors are unavailable due to a database connectivity issue, and we are currently investigating. Observability features and Astro Alerts are currently unavailable.

An potential Azure outage is resulting in some Azure clusters being unable to scale worker nodes. As a result, some tasks may fail. We are investigating internally and working with Azure to restore service as soon as possible.

We are continuing to investigate this issue.

Users may experience slow loading in the Astro UI, and Astro deploys may fail intermittently. We're investigating the issue and will provide updates as soon as more information becomes available.

Creation of AWS clusters is failing. At the moment, we do not think this impacts existing clusters, but we are working on getting confirmation for this.

We are continuing to investigate this issue.

We have confirmed that existing clusters are unaffected. We are testing a potential workaround to create AWS clusters.

We have found workers failing to heartbeat on several Airflow 3 deployments. Due to this tasks are unable run and eventually fail. This issue might be due to an update for the Astro Agent plugin that was rolled out today. We are currently investigating this.

We are currently investigating an issue with the auth layer of the Astro Cloud UI. We will update this incident as we have more information. Airflow deployments and task execution is unaffected.

Deployment health incidents are currently temporarily disabled for Astro https://www.astronomer.io/docs/astro/deployment-health-incidents There is no effect on DAG runs. They remain operational as normal.

We are continuing to investigate this issue.