Astronomer Outage History

We've identified a change that enabled GPU support for KubernetesPodOperator pods had an unintended side effect when reading pod specs without proper limits set in the expected format. We're working on a fix, if you notice any unexpected failures for KPO tasks in your Astro deployments, please open a support ticket.

We have identified the source of increased log generation volume, which is causing issues on the ingestion side. We're implementing mitigations now and are monitoring the results.

We are continuing to investigate and monitor this issue.

**The issue, according to Azure status page** Investigating a spike in 401 authentication errors We are actively investigating customer alerts of 401 authentication errors when pulling images from mcr.microsoft.com. We've identified a potential underlying factor related to a recent update made to a backed service and we are actively working on determining mitigation workstreams. More information will be provided shortly. This message was last updated at 23:04 UTC on 15 June 2026

We've identified an issue with `astro deploy`s not updating manifests in Astro Hosted clusters, and we're currently applying a workaround and are continuing to monitor the situation.

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.

A fix has been prepared and is moving through deployment. We will provide another update once the rollout is complete and validation is underway.

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

We have identified the issue and we are rolling out the fix for the affected deployments.

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.

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.

We are continuing to work on a fix for this issue.

We have identified the issue with Astro Alert's degraded performance and currently working on a fix.

There is an ongoing AWS outage, specifically in the us-east-1 region, as reported here: https://status.aws.amazon.com/ This outage is limiting our ability to troubleshoot and mitigate issues within customer clusters and Airflow deployments that are hosted in this region. All health indicators show these clusters and deployments remain healthy at this time, but we recommend not making any changes until the outage is over.

The fix has been applied. Things should be working as expected. We'll continue to monitor for the time being, but don't hesitate to reach out if you run into any issues.

We have identified the issue and are working on applying the fix.

While repairing the system, some Fernet keys (used to encrypt passwords in the Airflow connection configuration and variable configuration) are being restored. During this time, customers may see errors such as "could not create Fernet object: Incorrect padding", as well as variables or connections being marked as Invalid. The keys are currently being restored, and this error should disappear soon.

This issue is continuing to affect customers wishing to update their airflow deployments. The Astronomer team have identified the underlying issue and is actively working to deliver a fix.

An issue has been identified where images are successfully built and pushed, but the deployments are not being updated with the new images. This is intermittently affecting both CI/CD builds as well as builds triggered by the astro CLI tool. Astronomer will be monitoring and manually updating deployments with out of date images, but if you notice an image not being deployed, please contact support.

The issue has been identified and a fix is being implemented.

We are continuing to work on a fix for this issue.

We are continuing to work on a fix for this issue.

Any new images that are build using Astro Runtime 5.0.0 will fail to launch workers on Astro. Customers who have pushed Astro Runtime 5.0.0 images will be contacted by our support team.

We have identified the root cause of the issue and are working on a hotfix. We have disabled the selection of Astro Runtime 5.0.0 (and thus Airflow 2.3.0) until we can release that hotfix.