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.0Feb <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-1350Feb <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/statusFeb <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.

Astronomer Docs unavailable because of CDN outage

Nov <var data-var='date'>18</var>, <var data-var='time'>00:33</var> UTC Resolved - This incident has been resolved.Nov <var data-var='date'>17</var>, <var data-var='time'>18:42</var> UTC Monitoring - We have reverted the update that was rolled out. We are seeing worker pods in affected deployments running tasks now. We will continue monitoring this incident.Nov <var data-var='date'>17</var>, <var data-var='time'>18:13</var> UTC Investigating - 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.

Tasks unable to run due to worker issues

Nov <var data-var='date'>16</var>, <var data-var='time'>20:47</var> UTC Resolved - This incident has been resolved by Auth0.Nov <var data-var='date'>16</var>, <var data-var='time'>20:37</var> UTC Update - Auth0 has reported they are observing full recovery at this time. We're continuing to monitor but seeing full recovery on our side as well.Nov <var data-var='date'>16</var>, <var data-var='time'>20:18</var> UTC Monitoring - We are beginning to see successful login attempts and are continuing to monitor this issue.Nov <var data-var='date'>16</var>, <var data-var='time'>20:11</var> UTC Identified - This issue is related to an outage in Auth0's US-3 Public Cloud. For more information on that incident please see Auth0's incident here: https://status.auth0.com/incidents/hykzwhgmgn8zNov <var data-var='date'>16</var>, <var data-var='time'>20:06</var> UTC Investigating - 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.

Astro UI unavailable with "Invalid Authorization Code" error

Oct <var data-var='date'>31</var>, <var data-var='time'>11:03</var> UTC Resolved - The system is stable and healthy now. The issue has been resolved.Oct <var data-var='date'>30</var>, <var data-var='time'>16:38</var> UTC Monitoring - Deployment Health Incidents Enabled. We are monitoring the results.Oct <var data-var='date'>30</var>, <var data-var='time'>16:36</var> UTC Identified - The issue has been identified and a fix has been implemented.Oct <var data-var='date'>30</var>, <var data-var='time'>07:48</var> UTC Update - We are continuing to investigate this issue.Oct <var data-var='date'>30</var>, <var data-var='time'>07:42</var> UTC Investigating - 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.

Deployment Health Incidents Temporarily Disabled

Oct <var data-var='date'>30</var>, <var data-var='time'>04:27</var> UTC Resolved - Deployment Health Incidents have been temporarily disabled.Oct <var data-var='date'>30</var>, <var data-var='time'>00:58</var> UTC Investigating - https://www.astronomer.io/docs/astro/deployment-health-incidents

Deployment Health Incidents are not available

Oct <var data-var='date'>30</var>, <var data-var='time'>00:58</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'>30</var>, <var data-var='time'>00:51</var> UTC Monitoring - Deployment Health Incidents may not be working https://www.astronomer.io/docs/astro/deployment-health-incidentsOct <var data-var='date'>30</var>, <var data-var='time'>00:51</var> UTC Update - Deployment Health Incidents may not be working https://www.astronomer.io/docs/astro/deployment-health-incidentsOct <var data-var='date'>29</var>, <var data-var='time'>23:57</var> UTC Investigating - We are currently investigating this issue.

Astro UI performance may be severely degraded or unavailable

Oct <var data-var='date'>30</var>, <var data-var='time'>00:49</var> UTC Resolved - Resolved per Azure status; https://azure.status.microsoft/en-us/statusOct <var data-var='date'>29</var>, <var data-var='time'>16:35</var> UTC Update - We are continuing to monitor for any further affects from this Azure outage. You can follow Azure's status here: https://azure.status.microsoft/en-us/statusOct <var data-var='date'>29</var>, <var data-var='time'>16:05</var> UTC Monitoring - A fix has been implemented and we are monitoring the results.Oct <var data-var='date'>29</var>, <var data-var='time'>16:05</var> UTC Investigating - We are currently investigating an apparent issue with Azure's Front Door CDN that is causing DNS timeouts and unavailability of the Astro Cloud UI. Airflow deployments are unaffected and continue to process tasks. We have updated our DNS routing to bypass Front Door for now and are seeing access to the Cloud UI being restored.

Azure Front Door CDN issue causing timeouts to Astro Cloud UI

Oct <var data-var='date'>28</var>, <var data-var='time'>23:51</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'>28</var>, <var data-var='time'>19:39</var> UTC Monitoring - Customer deployments should no longer be affected, we are monitoring to confirm resolution.Oct <var data-var='date'>28</var>, <var data-var='time'>18:05</var> UTC Investigating - We are currently investigating this issue and have been notified by AWS of issues with VM scale ups in AWS us-east-1, specifically the use1-az2 AZ. We are working to identify affected deployments, as well as on mitigations.

Issues with EC2 scale up time in AWS us-east-1, use1-az2 Availability Zone causing node scale up issues for some deployment in AWs us-east-1

Oct <var data-var='date'>20</var>, <var data-var='time'>21:49</var> UTC Resolved - All Astronomer components have returned to a healthy state.Oct <var data-var='date'>20</var>, <var data-var='time'>18:19</var> UTC Update - We have observed pods that were previously stuck in the pending state slowly getting scheduled on EC2 nodes following mitigations applied by the AWS team. This should start resolving issues with task execution. We are actively monitoring the situation.Oct <var data-var='date'>20</var>, <var data-var='time'>16:30</var> UTC Monitoring - We have made a hotfix update to Astro to relieve the Airflow UI slowness in Azure, GCP, and in AWS regions other than us-east-1. We are continuing to monitor the impact of the change, but early signs indicate that the speed of the UI should be improving. This update has no effect on the issues unique to deployments in AWS us-east-1.Oct <var data-var='date'>20</var>, <var data-var='time'>16:12</var> UTC Update - We are continuing to investigate this issue.Oct <var data-var='date'>20</var>, <var data-var='time'>14:27</var> UTC Update - The AWS outage is affecting an internal tool, which is causing Airflow UI slowness in clusters running on all clouds (not just AWS). Our development team is working on a fix.Oct <var data-var='date'>20</var>, <var data-var='time'>13:08</var> UTC Update - We’re aware that the Airflow UI has been running very slowly following the recent AWS outage. Our team is actively investigating the issue.Oct <var data-var='date'>20</var>, <var data-var='time'>10:00</var> UTC Update - We are continuing to investigate this issue.Oct <var data-var='date'>20</var>, <var data-var='time'>10:00</var> UTC Investigating - We are aware of an ongoing AWS outage in the US-EAST-1 (N. Virginia) region that is impacting multiple AWS services and related infrastructure components. Customers with Astro clusters and deployments hosted on AWS may experience degraded performance, failed task executions, or delays in accessing their environments. Our team is actively monitoring the situation and assessing the impact across affected deployments. For real-time updates from AWS, please refer to their Service Health Dashboard - https://health.aws.amazon.com/health/status Next update will be provided as more information becomes available.

AWS Outage Impacting Astro Deployments

Oct <var data-var='date'> 6</var>, <var data-var='time'>22:08</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'> 6</var>, <var data-var='time'>17:52</var> UTC Monitoring - The root cause of this incident has been fully identified, and our engineering teams are continuing to work on implementing mitigations. We are also continuing to monitor this issue and the underlying systems associated. Incidence of this issue has dropped significantly, however degraded performance is still possible.Oct <var data-var='date'> 6</var>, <var data-var='time'>16:08</var> UTC Identified - We are investigating this issue and have identified the source of the issue and are putting mitigations in place. Airflow deployment task execution is unaffected. Dag triggering via Airflow API may experience intermittent issues.

Internal API intermittent outage causing slow UI loading, intermittent Airflow API issues

Oct <var data-var='date'> 1</var>, <var data-var='time'>22:17</var> UTC Resolved - This incident has been resolved.Oct <var data-var='date'> 1</var>, <var data-var='time'>18:30</var> UTC Monitoring - The number of affected deployments has dropped significantly. Many deployments continue to inaccurately report as unhealthy, while their schedulers and other underlying components are working. We believe that all schedulers are no longer experiencing this issue, but we are verifying this.Oct <var data-var='date'> 1</var>, <var data-var='time'>17:16</var> UTC Investigating - We are currently investigating this issue.

Is Astro down?

Astro status is UP

Lastest published events

Deployment changes fail due to an unrelated "hibernation" error

Deployment CRUD Operations Experiencing Failures

Astro deployments in GCP us-central-1 experiencing issues

Astro Services, Components and Regions

Recent Astro events

Deployment changes fail due to an unrelated "hibernation" error

Deployment CRUD Operations Experiencing Failures

Astro deployments in GCP us-central-1 experiencing issues

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

Services Unavailable

Astro Maintenance - UI and API unavailable

Get your FREE account now,
5 monitors included!

Is Astro down?

Astro status is UP

Lastest published events

Deployment changes fail due to an unrelated "hibernation" error

Deployment CRUD Operations Experiencing Failures

Astro deployments in GCP us-central-1 experiencing issues

Astro Services, Components and Regions

Recent Astro events

Deployment changes fail due to an unrelated "hibernation" error

Deployment CRUD Operations Experiencing Failures

Astro deployments in GCP us-central-1 experiencing issues

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

Services Unavailable

Astro Maintenance - UI and API unavailable

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!