May <var data-var='date'> 9</var>, <var data-var='time'>01:43</var> UTC Resolved - AWS has confirmed recovery in the affected Availability Zone (use1-az4), and system performance has returned to normal levels. We are no longer observing elevated task failures or latency in the AWS us-east-1 region. Any previously impacted workloads should now be operating as expected. If you continue to experience issues, please reach out to Astronomer Support for assistance. May <var data-var='date'> 8</var>, <var data-var='time'>07:45</var> UTC Monitoring - We are continuing to monitor the situation as AWS works toward full recovery in the affected Availability Zone. At this time, we are seeing signs of stabilization, and most transient failures should continue to self-resolve. We will provide further updates once AWS confirms that the issue has been fully resolved. May <var data-var='date'> 8</var>, <var data-var='time'>07:43</var> UTC Investigating - 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

Increased Task Failures in US-East-1 (AWS) - AWS Incident

May <var data-var='date'> 7</var>, <var data-var='time'>14:24</var> UTC Resolved - The incident has been resolved. May <var data-var='date'> 7</var>, <var data-var='time'>13:49</var> UTC Monitoring - A fix has been implemented, and we are monitoring the results. May <var data-var='date'> 7</var>, <var data-var='time'>12:57</var> UTC Update - A fix has been prepared and is moving through deployment. We will provide another update once the rollout is complete and validation is underway. May <var data-var='date'> 7</var>, <var data-var='time'>11:15</var> UTC Identified - We have identified the cause of the delayed delivery for some time-based alerts and are implementing a fix. We will provide another update once the fix has been deployed and validated. May <var data-var='date'> 7</var>, <var data-var='time'>10:31</var> UTC Investigating - 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.

Delayed delivery for some time-based alerts

May <var data-var='date'> 6</var>, <var data-var='time'>20:05</var> UTC Resolved - Our team has determined this only affects internal access, Astro end users are unaffected. May <var data-var='date'> 6</var>, <var data-var='time'>19:56</var> UTC Investigating - Attempting to access the dags page in the Airflow UI results in a 403 Forbidden error. This should not be affecting task execution.

Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.

May <var data-var='date'> 4</var>, <var data-var='time'>20:15</var> UTC Resolved - This incident is now resolved, and all Cost Breakdown data is now up to date. The issue that caused the delay has been fixed and should not recur. May <var data-var='date'> 4</var>, <var data-var='time'>10:56</var> UTC Update - We are continuing to investigate this issue. May <var data-var='date'> 4</var>, <var data-var='time'>10:56</var> UTC Investigating - 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.

Dashboard cost breakdown data delays

Apr <var data-var='date'>28</var>, <var data-var='time'>00:16</var> UTC Resolved - We rolled back a change we made to our authentication system. Any image pushes or config changes to a deployment that occurred after our rollback caused the deployment to fix itself, which is why so many people found their 403s resolved themselves after some time. Apr <var data-var='date'>27</var>, <var data-var='time'>22:05</var> UTC Update - We are continuing to investigate this issue. Apr <var data-var='date'>27</var>, <var data-var='time'>22:04</var> UTC Investigating - It seems to be only in AWS clusters for now. We have a workaround we can apply while we investigate.

Airflow UI showing 403s for some customers

Apr <var data-var='date'>25</var>, <var data-var='time'>05:05</var> UTC Resolved - Azure has confirmed the issue is resolved and services are back to normal. This incident is now closed. For more details, see the Azure incident history: https://azure.status.microsoft/en-us/status/history/ Apr <var data-var='date'>25</var>, <var data-var='time'>03:56</var> UTC Monitoring - Azure has fixed the issue, and services are back to normal in East US. We are monitoring to make sure everything stays stable. Apr <var data-var='date'>24</var>, <var data-var='time'>17:28</var> UTC Identified - Azure East US has reported multi-service impact that is affecting Astro deployments in the region. For more information on Azure outage, please visit: https://azure.status.microsoft/en-us/status

Azure East US multiservice outage impacting Astro deployments in the region

Apr <var data-var='date'>17</var>, <var data-var='time'>11:47</var> UTC Resolved - This issue has been resolved. Apr <var data-var='date'>17</var>, <var data-var='time'>10:01</var> UTC Monitoring - The fix has been implemented, and we are now monitoring the deployments. Apr <var data-var='date'>17</var>, <var data-var='time'>08:05</var> UTC Identified - We have identified the issue and we are rolling out the fix for the affected deployments. Apr <var data-var='date'>17</var>, <var data-var='time'>08:04</var> UTC Investigating - 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.

Terminating Workers Accepting Tasks Causing Failures in Astro Executor

Apr <var data-var='date'>16</var>, <var data-var='time'>22:25</var> UTC Resolved - Astronomer Runtime 3.2-2 has been released with the fix. Apr <var data-var='date'>16</var>, <var data-var='time'>18:04</var> UTC Identified - We have identified that Runtime 3.2-1 is incompatible with the Astro Environment Manager. Any Connections or Variables stored at the Workspace level will not be available on deployments running 3.2-1. For this reason, we have disallowed the use of 3.2-1 for any deployments which are not already on that version. We are working to release a 3.2-2 version that is properly compatible as quickly as possible.

Runtime 3.2-1 Yanked - Incompatible with Env Manager

Apr <var data-var='date'>13</var>, <var data-var='time'>22:11</var> UTC Resolved - **RESOLVED** – Azure West Europe Cluster Capacity Issue We have resolved a capacity issue affecting our Azure West Europe (westeurope) shared cluster that occurred between 1:34 PM and 3:09 PM PDT on April 13. During this window, the cluster reached its vCPU quota, causing some deployments to become unhealthy. Our team immediately engaged Azure support and provisioned additional capacity as a temporary workaround, allowing all workloads to resume scheduling. All services are now fully operational and healthy. We're working with Azure on a permanent quota increase to prevent recurrence. We apologize for any disruption. If you experienced issues, please contact our support team. Apr <var data-var='date'>13</var>, <var data-var='time'>22:10</var> UTC Update - We are continuing to work on a fix for this issue. Apr <var data-var='date'>13</var>, <var data-var='time'>21:44</var> UTC Identified - We are currently investigating an issue affecting deployments in our Azure West Europe region. Some customer deployments are experiencing degraded performance due to a compute resource constraint in our shared infrastructure. Our engineering team has identified that the region has reached its vCPU quota limit for a specific compute type, which is preventing new resources from being provisioned. We have opened a high-priority support request with Azure to increase this quota and are actively working with our Azure representative to expedite the approval. We will provide updates as soon as we have more information about the timeline for resolution. We apologize for any disruption this may cause to your service.

Degraded service for some deployments in Azure West Europe

Apr <var data-var='date'>13</var>, <var data-var='time'>11:12</var> UTC Resolved - The issue has been resolved. Over the weekend, we observed a degradation in alert performance. With the fix now applied, any missed alerts are expected to be delivered now, and new alerts will be triggered without latency. Alerting has returned to normal, and there is no ongoing delay. All alerts should now fire as expected. Apr <var data-var='date'>13</var>, <var data-var='time'>00:40</var> UTC Monitoring - We have applied a fix for the Astro Alerts degraded performance and currently monitoring it. Apr <var data-var='date'>13</var>, <var data-var='time'>00:18</var> UTC Identified - We have identified the issue with Astro Alert's degraded performance and currently working on a fix. Apr <var data-var='date'>12</var>, <var data-var='time'>22:56</var> UTC Investigating - We are currently investigating an issue causing false positive alerts via Astro Alerts. Our team is actively investigating the issue.

Astro Alerts Degraded Performance

Apr <var data-var='date'> 1</var>, <var data-var='time'>19:49</var> UTC Resolved - This incident has been resolved. Apr <var data-var='date'> 1</var>, <var data-var='time'>18:32</var> UTC Update - We are continuing to work on a fix for this issue. Apr <var data-var='date'> 1</var>, <var data-var='time'>18:31</var> UTC Identified - The issue has been identified and a fix is being implemented.

Deployment changes fail due to an unrelated "hibernation" error

Mar <var data-var='date'>11</var>, <var data-var='time'>09:54</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'>11</var>, <var data-var='time'>09:51</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>11</var>, <var data-var='time'>09:45</var> UTC Update - We are continuing to investigate this issue. Mar <var data-var='date'>11</var>, <var data-var='time'>09:45</var> UTC Investigating - 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.

Deployment CRUD Operations Experiencing Failures

Mar <var data-var='date'> 9</var>, <var data-var='time'>16:11</var> UTC Resolved - The GKE incident is now resolved per Google, and we are seeing that all related issues appear to have cleared up on Astro. If you are still experiencing an issue, please raise a support ticket. Mar <var data-var='date'> 9</var>, <var data-var='time'>15:30</var> UTC Identified - We are seeing signs of recovery across some affected clusters. Mar <var data-var='date'> 9</var>, <var data-var='time'>13:53</var> UTC Update - Google has confirmed to Astronomer that this is an issue with GKE in the region. We are following the issue closely. Mar <var data-var='date'> 9</var>, <var data-var='time'>13:29</var> UTC Investigating - 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.

Astro deployments in GCP us-central-1 experiencing issues

Mar <var data-var='date'> 5</var>, <var data-var='time'>23:05</var> UTC Resolved - This incident has been resolved. Mar <var data-var='date'> 5</var>, <var data-var='time'>16:49</var> UTC Monitoring - Azure confirmed that the fix has been successfully deployed to East US 2 region. We are monitoring the results. Mar <var data-var='date'> 4</var>, <var data-var='time'>14:31</var> UTC Identified - We have identified the root cause of the autoscaling issue affecting certain deployments on the Shared Azure Cluster in the US-East2 region. The issue is related to underlying infrastructure behaviour within the cloud provider environment. Azure has acknowledged the issue and is currently rolling out a hotfix across regions. We are actively monitoring the rollout and will provide further updates as they become available. Mar <var data-var='date'> 4</var>, <var data-var='time'>14:10</var> UTC Investigating - 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.

Degraded Worker Autoscaling on Hosted Shared Azure Cluster (US-East2)

Feb <var data-var='date'>28</var>, <var data-var='time'>21:32</var> UTC Resolved - Astro Observe is fully operational! Incident is now resolved. Feb <var data-var='date'>28</var>, <var data-var='time'>19:36</var> UTC Identified - Maintenance completed. We are currently looking into bringing Astro Observe up to operational. Feb <var data-var='date'>28</var>, <var data-var='time'>19:10</var> UTC Investigating - 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.

Services Unavailable

Feb <var data-var='date'>28</var>, <var data-var='time'>19:00</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'>28</var>, <var data-var='time'>16:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Feb <var data-var='date'>14</var>, <var data-var='time'>03:15</var> UTC Scheduled - The Astro Control plane will be undergoing maintenance that will require downtime of the Astro UI and Astro API. DAGs and tasks of existing deployments will continue to run normally even if they are not viewable via UI, unless the task itself uses the API as part of its operation (such as in cases where a task triggers a DAG in a different Astro deployment).

Astro Maintenance - UI and API unavailable

Feb <var data-var='date'>24</var>, <var data-var='time'>22:49</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>24</var>, <var data-var='time'>22:27</var> UTC Monitoring - 13.5.0 has been officially yanked from the registry. 13.5.1 will follow but for now stay on 13.4.0 Feb <var data-var='date'>24</var>, <var data-var='time'>21:58</var> UTC Identified - https://www.astronomer.io/docs/runtime/runtime-release-notes#astro-runtime-1350 Feb <var data-var='date'>24</var>, <var data-var='time'>21:51</var> UTC Investigating - We are currently investigating this issue.

Upgrading to Astronomer Runtime 13.5.0 causes 'Open Airflow' button to fail until cookies are cleared

Feb <var data-var='date'>13</var>, <var data-var='time'>12:16</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'>13</var>, <var data-var='time'>11:18</var> UTC Monitoring - A fix has been implemented and we are monitoring the results. Feb <var data-var='date'>13</var>, <var data-var='time'>11:11</var> UTC Update - Observability processors are unavailable due to a database connectivity issue, and we are currently investigating. Observability features and Astro Alerts are currently unavailable. Feb <var data-var='date'>13</var>, <var data-var='time'>10:54</var> UTC Investigating - We are currently investigating this issue.

Observability Product Outage

Feb <var data-var='date'> 9</var>, <var data-var='time'>18:00</var> UTC Completed - The scheduled maintenance has been completed. Feb <var data-var='date'> 9</var>, <var data-var='time'>17:00</var> UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>26</var>, <var data-var='time'>17:56</var> UTC Scheduled - On or shortly after February 9, 2026, the Astro Control Plane's outbound IP addresses will expand to also include 104.43.242.104/30. If you have allowlisted the Control Plane IP addresses for purposes of controlling access by the Astro IDE, Astro Observe Snowflake integration, or webhooks from Astro Alerts, please add this new CIDR range to your allowlist or your firewall may block some traffic from these services. For Astro users who have not applied a firewall to these services, no change is needed. Normal operation of Airflow tasks and DAGs will not be affected. External IPs for Deployments are also not affected by this change.

Additional IP Addresses Added to Control Plane

Feb <var data-var='date'> 5</var>, <var data-var='time'>13:42</var> UTC Resolved - This incident has been resolved. Feb <var data-var='date'> 5</var>, <var data-var='time'>13:42</var> UTC Monitoring - The fix has been applied to the affected deployments, and the issue should no longer be observed. Feb <var data-var='date'> 5</var>, <var data-var='time'>12:41</var> UTC Identified - We have identified an issue with some Astro Executor deployments where the graceful termination period of workers is not respected, leading to potential task failures. We are rolling out a fix for the affected Deployments

Task failures on deployments using AstroExecutor

Feb <var data-var='date'> 3</var>, <var data-var='time'>08:56</var> UTC Resolved - Mitigations have been fully applied across all affected regions by Azure, and validations confirm that configurations have been successfully updated. Customers should now see full recovery of service management operations, and dependent services are operating as expected. Feb <var data-var='date'> 3</var>, <var data-var='time'>01:50</var> UTC Update - We are now seeing additional clusters being affected. Issue is still ongoing. Feb <var data-var='date'> 3</var>, <var data-var='time'>00:23</var> UTC Monitoring - We are still waiting on confirmation from Azure that the issue has passed, but we are no longer seeing impact to Astronomer workloads. Feb <var data-var='date'> 2</var>, <var data-var='time'>21:46</var> UTC Identified - Azure has confirmed the outage. Please see their status page for additional information https://azure.status.microsoft/en-us/status Feb <var data-var='date'> 2</var>, <var data-var='time'>20:43</var> UTC Update - We are continuing to investigate this issue. Feb <var data-var='date'> 2</var>, <var data-var='time'>20:43</var> UTC Investigating - 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.

Some Azure clusters unable to scale worker nodes.

Jan <var data-var='date'>29</var>, <var data-var='time'>11:33</var> UTC Resolved - The Astro Core API issue has been fixed, and all components are now fully operational. Jan <var data-var='date'>29</var>, <var data-var='time'>11:02</var> UTC Monitoring - Our engineering team has applied a fix that should help mitigate the issue. We are currently monitoring the situation and are seeing internal improvements. We will continue to provide updates as we learn more. Jan <var data-var='date'>29</var>, <var data-var='time'>10:30</var> UTC Investigating - 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.

Astro Core API performance degradation

Jan <var data-var='date'>17</var>, <var data-var='time'>00:19</var> UTC Resolved - This incident has been resolved. Jan <var data-var='date'>17</var>, <var data-var='time'>00:14</var> UTC Update - All system functionality has been restored and is operational. Jan <var data-var='date'>16</var>, <var data-var='time'>23:39</var> UTC Update - The fix has been released and verified and it will become available across Astronomer infrastructure over the next hour. Jan <var data-var='date'>16</var>, <var data-var='time'>20:22</var> UTC Identified - We have identified the root cause and are working on releasing a fix. Jan <var data-var='date'>16</var>, <var data-var='time'>18:08</var> UTC Update - We have confirmed that existing clusters are unaffected. We are testing a potential workaround to create AWS clusters. Jan <var data-var='date'>16</var>, <var data-var='time'>17:00</var> UTC Update - We are continuing to investigate this issue. Jan <var data-var='date'>16</var>, <var data-var='time'>16:59</var> UTC Investigating - 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.

AWS Cluster Creation is Failing

Nov <var data-var='date'>24</var>, <var data-var='time'>22:11</var> UTC Resolved - The Astro Core API issue is fixed and all components are operational now. Nov <var data-var='date'>24</var>, <var data-var='time'>20:50</var> UTC Monitoring - We have identified the degraded performance in Astro Core API and applied the fix. We are currently monitoring the issue. Nov <var data-var='date'>24</var>, <var data-var='time'>20:49</var> UTC Update - We are continuing to investigate this issue. Nov <var data-var='date'>24</var>, <var data-var='time'>20:20</var> UTC Investigating - Users may experience slow loading in the Astro UI. We’re investigating the issue and will provide updates as soon as we have more information.

Nov <var data-var='date'>18</var>, <var data-var='time'>15:31</var> UTC Resolved - This incident has been resolved. Nov <var data-var='date'>18</var>, <var data-var='time'>14:34</var> UTC Monitoring - Docs appear to be back up at the moment, but because Cloudflare has not marked the incident as resolved, we are continuing to monitor. Nov <var data-var='date'>18</var>, <var data-var='time'>13:26</var> UTC Identified - Astronomer's Documentation at astronomer.io/docs is currently returning a 500 error because of an issue with our CDN, Cloudflare. We are tracking the status of their ongoing incident here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 All Astro services are currently working as intended. No Astro services other than documentation rely on Cloudflare.

Is Astro down?

Astro status is UP

Lastest published events

Increased Task Failures in US-East-1 (AWS) - AWS Incident

Delayed delivery for some time-based alerts

Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.

Astro Services, Components and Regions

Recent Astro events

Increased Task Failures in US-East-1 (AWS) - AWS Incident

Delayed delivery for some time-based alerts

Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.

Dashboard cost breakdown data delays

Airflow UI showing 403s for some customers

Azure East US multiservice outage impacting Astro deployments in the region

Get your FREE account now,
5 monitors included!

Is Astro down?

Astro status is UP

Lastest published events

Increased Task Failures in US-East-1 (AWS) - AWS Incident

Delayed delivery for some time-based alerts

Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.

Astro Services, Components and Regions

Recent Astro events

Increased Task Failures in US-East-1 (AWS) - AWS Incident

Delayed delivery for some time-based alerts

Deployments on Astronomer Runtime 3.2-3 are returning 403 errors when accessing dags page.

Dashboard cost breakdown data delays

Airflow UI showing 403s for some customers

Azure East US multiservice outage impacting Astro deployments in the region

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!