Astronomer Outage History

The Astro Core API is showing an elevated number of errors. We are investigating actively and will update as soon as we know more. Next update will be within the next 30 minutes.

Our metrics indicate no impact on existing tasks and Dag Runs. They are continuing to run successfully. We are continuing to investigate what is causing the API and UI errors and are attempting a workaround.

We have identified several hosted deployments where tasks are getting stuck in the queued state and failing. This is happening the worker autoscaler is having issues with scaling up workers to run tasks. We are investigating the cause of this.

We are investigation reports that the Deployments view of the Astro Cloud UI is unavailable. We will update as we know more.

We have confirmed that task execution is unaffected. We're continuing to investigate.

We are currently investigating an issue affecting deployment access, authentication, and related services for multiple customers. Some users may experience 401 errors when using organization-based Astronomer URLs (ORG_ID.astronomer.run), as well as "RBAC: access denied" errors or difficulty viewing DAGs in the Astronomer UI.

We're continuing to investigate the issue affecting access/auth to some deployments and services. We will follow up with an update no later than 5:30 AM UTC on Friday, September 4, 2026, or sooner if we have something to share.

Our metrics pipeline is falsely displaying spikes in scheduler heartbeat metrics, despite underlying component health.

We have identified an issue affecting an internal rollout related to the `pre_execute` Airflow hook in Astro Hosted. We have identified a fix and are rolling it out across the fleet. We are monitoring the rollout and will provide further updates as it progresses.

We are investigating intermittent connectivity issues affecting clusters in Azure Central US when calling Astronomer APIs. This may prevent or delay attempts to create, update, or delete Airflow Deployments. Our engineering team is actively investigating the issue and working to restore normal service.

We are currently investigating an issue with platform log ingestion for Astro. Logs may not be available in the Cloud UI.

We are continuing to investigate this issue, and will provide another update in 30mins or as new information is available.

We have detected node scaling issues in the Azure EastUS2 region and are currently investigating.

We are investigating a spike in issues in AWS us-east-1 region, affecting node scale-up. This will create issues with workers scaling up and potentially new tasks starting

AWS has published a status update for this issue. We are actively monitoring their progress and will continue to share updates.

We are currently investigating this issue.

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 we can apply 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.