Astronomer Outage History
Astronomer is up right nowPingoru has recorded 65 incidents for Astronomer: 64 in the last 12 months and 18 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 13 | 36 of 720 (5%) |
| May 2026 | 8 | 31 of 744 (4%) |
| June 2026 | 4 | 3 of 720 (0%) |
| July 2026 | 3 | 12 of 744 (2%) |
| August 2026 | 4 | 324 of 744 (43%) |
| September 2026 | 5 | 38 of 720 (5%) |
| October 2026 | 8 | 305 of 590 (52%) |
Incidents, newest first
Major April 27, 2026 Airflow UI showing 403s for some customers 2h 9m
Started Apr 27, 2026, 10:06 PM UTC· resolved Apr 28, 2026, 12:16 AM UTC
- investigating Apr 27, 2026, 10:06 PM UTC
It seems to be only in AWS clusters for now. We have a workaround we can apply while we investigate.
- investigating Apr 27, 2026, 10:06 PM UTC
We are continuing to investigate this issue.
- resolved Apr 28, 2026, 01:06 AM UTC
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.
Minor April 24, 2026 Azure East US multiservice outage impacting Astro deployments in the region 11h 37m
Started Apr 24, 2026, 05:28 PM UTC· resolved Apr 25, 2026, 05:05 AM UTC
- identified Apr 24, 2026, 05:28 PM UTC
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
- monitoring Apr 25, 2026, 04:08 AM UTC
Azure has fixed the issue, and services are back to normal in East US. We are monitoring to make sure everything stays stable.
- resolved Apr 25, 2026, 05:09 AM UTC
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/
Minor April 17, 2026 Terminating Workers Accepting Tasks Causing Failures in Astro Executor 3h 39m
Started Apr 17, 2026, 08:08 AM UTC· resolved Apr 17, 2026, 11:47 AM UTC
- investigating Apr 17, 2026, 08:08 AM UTC
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.
- identified Apr 17, 2026, 08:08 AM UTC
We have identified the issue and we are rolling out the fix for the affected deployments.
- monitoring Apr 17, 2026, 10:08 AM UTC
The fix has been implemented, and we are now monitoring the deployments.
- resolved Apr 17, 2026, 12:07 PM UTC
This issue has been resolved.
Major April 16, 2026 Runtime 3.2-1 Yanked - Incompatible with Env Manager 4h 18m
Started Apr 16, 2026, 06:06 PM UTC· resolved Apr 16, 2026, 10:25 PM UTC
- identified Apr 16, 2026, 06:06 PM UTC
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.
- resolved Apr 16, 2026, 11:06 PM UTC
Astronomer Runtime 3.2-2 has been released with the fix.
Notice April 13, 2026 Degraded service for some deployments in Azure West Europe 4m
Started Apr 13, 2026, 10:07 PM UTC· resolved Apr 13, 2026, 10:11 PM UTC
- identified Apr 13, 2026, 10:07 PM UTC
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.
- identified Apr 13, 2026, 11:05 PM UTC
We are continuing to work on a fix for this issue.
- resolved Apr 13, 2026, 11:05 PM UTC
**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.
Minor April 12, 2026 Astro Alerts Degraded Performance 12h 15m
Started Apr 12, 2026, 10:56 PM UTC· resolved Apr 13, 2026, 11:12 AM UTC
- investigating Apr 12, 2026, 10:56 PM UTC
We are currently investigating an issue causing false positive alerts via Astro Alerts. Our team is actively investigating the issue.
- identified Apr 13, 2026, 12:18 AM UTC
We have identified the issue with Astro Alert's degraded performance and currently working on a fix.
- monitoring Apr 13, 2026, 12:40 AM UTC
We have applied a fix for the Astro Alerts degraded performance and currently monitoring it.
- resolved Apr 13, 2026, 12:07 PM UTC
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.
Major April 1, 2026 Deployment changes fail due to an unrelated "hibernation" error 1h 18m Deployment Management, Deployment Management
Started Apr 01, 2026, 06:31 PM UTC· resolved Apr 01, 2026, 07:49 PM UTC
- identified Apr 01, 2026, 06:31 PM UTC
The issue has been identified and a fix is being implemented.
- identified Apr 01, 2026, 06:32 PM UTC
We are continuing to work on a fix for this issue.
- resolved Apr 01, 2026, 07:49 PM UTC
This incident has been resolved.
Major March 11, 2026 Deployment CRUD Operations Experiencing Failures 9m Deployment Management, Deployment Management
Started Mar 11, 2026, 09:45 AM UTC· resolved Mar 11, 2026, 09:54 AM UTC
- investigating Mar 11, 2026, 09:45 AM UTC
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.
- investigating Mar 11, 2026, 09:45 AM UTC
We are continuing to investigate this issue.
- monitoring Mar 11, 2026, 09:51 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Mar 11, 2026, 09:54 AM UTC
This incident has been resolved.
Major March 9, 2026 Astro deployments in GCP us-central-1 experiencing issues 2h 41m Scheduling and Running DAGs and Tasks, Scheduling and Running DAGs and Tasks, Deployment Management, Deployment Management
Started Mar 09, 2026, 01:29 PM UTC· resolved Mar 09, 2026, 04:11 PM UTC
- investigating Mar 09, 2026, 01:29 PM UTC
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.
- investigating Mar 09, 2026, 01:53 PM UTC
Google has confirmed to Astronomer that this is an issue with GKE in the region. We are following the issue closely.
- identified Mar 09, 2026, 03:30 PM UTC
We are seeing signs of recovery across some affected clusters.
- resolved Mar 09, 2026, 04:11 PM UTC
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.
Minor March 4, 2026 Degraded Worker Autoscaling on Hosted Shared Azure Cluster (US-East2) 1d 8h Scheduling and Running DAGs and Tasks
Started Mar 04, 2026, 02:10 PM UTC· resolved Mar 05, 2026, 11:05 PM UTC
- investigating Mar 04, 2026, 02:10 PM UTC
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.
- identified Mar 04, 2026, 02:31 PM UTC
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.
- monitoring Mar 05, 2026, 04:49 PM UTC
Azure confirmed that the fix has been successfully deployed to East US 2 region. We are monitoring the results.
- resolved Mar 05, 2026, 11:05 PM UTC
This incident has been resolved.
Minor February 28, 2026 Services Unavailable 2h 22m Deployment Access, Deployment Management, Cloud UI, Astro Observe and 1 more
Started Feb 28, 2026, 07:10 PM UTC· resolved Feb 28, 2026, 09:32 PM UTC
- investigating Feb 28, 2026, 07:10 PM UTC
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.
- identified Feb 28, 2026, 07:36 PM UTC
Maintenance completed. We are currently looking into bringing Astro Observe up to operational.
- resolved Feb 28, 2026, 09:32 PM UTC
Astro Observe is fully operational! Incident is now resolved.
Major February 24, 2026 Upgrading to Astronomer Runtime 13.5.0 causes 'Open Airflow' button to fail until cookies are cleared 57m Deployment Access, Deployment Access, Deployment Management, Deployment Management
Started Feb 24, 2026, 09:51 PM UTC· resolved Feb 24, 2026, 10:49 PM UTC
- investigating Feb 24, 2026, 09:51 PM UTC
We are currently investigating this issue.
- identified Feb 24, 2026, 09:58 PM UTC
https://www.astronomer.io/docs/runtime/runtime-release-notes#astro-runtime-1350
- monitoring Feb 24, 2026, 10:27 PM UTC
13.5.0 has been officially yanked from the registry. 13.5.1 will follow but for now stay on 13.4.0
- resolved Feb 24, 2026, 10:49 PM UTC
This incident has been resolved.
Critical February 13, 2026 Observability Product Outage 1h 22m Astro Observe
Started Feb 13, 2026, 10:54 AM UTC· resolved Feb 13, 2026, 12:16 PM UTC
- investigating Feb 13, 2026, 10:54 AM UTC
We are currently investigating this issue.
- investigating Feb 13, 2026, 11:11 AM UTC
Observability processors are unavailable due to a database connectivity issue, and we are currently investigating. Observability features and Astro Alerts are currently unavailable.
- monitoring Feb 13, 2026, 11:18 AM UTC
A fix has been implemented and we are monitoring the results.
- resolved Feb 13, 2026, 12:16 PM UTC
This incident has been resolved.
Major February 5, 2026 Task failures on deployments using AstroExecutor 1h Scheduling and Running DAGs and Tasks
Started Feb 05, 2026, 12:41 PM UTC· resolved Feb 05, 2026, 01:42 PM UTC
- identified Feb 05, 2026, 12:41 PM UTC
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
- monitoring Feb 05, 2026, 01:42 PM UTC
The fix has been applied to the affected deployments, and the issue should no longer be observed.
- resolved Feb 05, 2026, 01:42 PM UTC
This incident has been resolved.
Major February 2, 2026 Some Azure clusters unable to scale worker nodes. 12h 13m Scheduling and Running DAGs and Tasks
Started Feb 02, 2026, 08:43 PM UTC· resolved Feb 03, 2026, 08:56 AM UTC
- investigating Feb 02, 2026, 08:43 PM UTC
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.
- investigating Feb 02, 2026, 08:43 PM UTC
We are continuing to investigate this issue.
- identified Feb 02, 2026, 09:46 PM UTC
Azure has confirmed the outage. Please see their status page for additional information https://azure.status.microsoft/en-us/status
- monitoring Feb 03, 2026, 12:23 AM UTC
We are still waiting on confirmation from Azure that the issue has passed, but we are no longer seeing impact to Astronomer workloads.
- monitoring Feb 03, 2026, 01:50 AM UTC
We are now seeing additional clusters being affected. Issue is still ongoing.
- resolved Feb 03, 2026, 08:56 AM UTC
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.
Minor January 29, 2026 Astro Core API performance degradation 1h 3m Scheduling and Running DAGs and Tasks, Scheduling and Running DAGs and Tasks, Deployment Access, Deployment Access and 11 more
Started Jan 29, 2026, 10:30 AM UTC· resolved Jan 29, 2026, 11:33 AM UTC
- investigating Jan 29, 2026, 10:30 AM UTC
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.
- monitoring Jan 29, 2026, 11:02 AM UTC
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.
- resolved Jan 29, 2026, 11:33 AM UTC
The Astro Core API issue has been fixed, and all components are now fully operational.
Major January 16, 2026 AWS Cluster Creation is Failing 7h 20m Deployment Management
Started Jan 16, 2026, 04:59 PM UTC· resolved Jan 17, 2026, 12:19 AM UTC
- investigating Jan 16, 2026, 04:59 PM UTC
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.
- investigating Jan 16, 2026, 05:00 PM UTC
We are continuing to investigate this issue.
- investigating Jan 16, 2026, 06:08 PM UTC
We have confirmed that existing clusters are unaffected. We are testing a potential workaround to create AWS clusters.
- identified Jan 16, 2026, 08:22 PM UTC
We have identified the root cause and are working on releasing a fix.
- identified Jan 16, 2026, 11:39 PM UTC
The fix has been released and verified and it will become available across Astronomer infrastructure over the next hour.
- identified Jan 17, 2026, 12:14 AM UTC
All system functionality has been restored and is operational.
- resolved Jan 17, 2026, 12:19 AM UTC
This incident has been resolved.
Notice November 18, 2025 Astronomer Docs unavailable because of CDN outage 2h 4m
Started Nov 18, 2025, 01:26 PM UTC· resolved Nov 18, 2025, 03:31 PM UTC
- identified Nov 18, 2025, 01:26 PM UTC
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.
- monitoring Nov 18, 2025, 02:34 PM UTC
Docs appear to be back up at the moment, but because Cloudflare has not marked the incident as resolved, we are continuing to monitor.
- resolved Nov 18, 2025, 03:31 PM UTC
This incident has been resolved.
Major November 17, 2025 Tasks unable to run due to worker issues 6h 19m Scheduling and Running DAGs and Tasks, Scheduling and Running DAGs and Tasks
Started Nov 17, 2025, 06:13 PM UTC· resolved Nov 18, 2025, 12:33 AM UTC
- investigating Nov 17, 2025, 06:13 PM UTC
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.
- monitoring Nov 17, 2025, 06:42 PM UTC
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.
- resolved Nov 18, 2025, 12:33 AM UTC
This incident has been resolved.
Major November 16, 2025 Astro UI unavailable with "Invalid Authorization Code" error 41m Cloud UI, Cloud UI, Cloud API, Cloud API
Started Nov 16, 2025, 08:06 PM UTC· resolved Nov 16, 2025, 08:47 PM UTC
- investigating Nov 16, 2025, 08:06 PM UTC
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.
- identified Nov 16, 2025, 08:11 PM UTC
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/hykzwhgmgn8z
- monitoring Nov 16, 2025, 08:18 PM UTC
We are beginning to see successful login attempts and are continuing to monitor this issue.
- monitoring Nov 16, 2025, 08:37 PM UTC
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.
- resolved Nov 16, 2025, 08:47 PM UTC
This incident has been resolved by Auth0.
Minor October 30, 2025 Deployment Health Incidents Temporarily Disabled 1d 3h
Started Oct 30, 2025, 07:42 AM UTC· resolved Oct 31, 2025, 11:03 AM UTC
- investigating Oct 30, 2025, 07:42 AM UTC
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.
- investigating Oct 30, 2025, 07:48 AM UTC
We are continuing to investigate this issue.
- identified Oct 30, 2025, 04:36 PM UTC
The issue has been identified and a fix has been implemented.
- monitoring Oct 30, 2025, 04:38 PM UTC
Deployment Health Incidents Enabled. We are monitoring the results.
- resolved Oct 31, 2025, 11:03 AM UTC
The system is stable and healthy now. The issue has been resolved.
Major October 30, 2025 Deployment Health Incidents are not available 3h 28m Deployment Management, Deployment Management
Started Oct 30, 2025, 12:58 AM UTC· resolved Oct 30, 2025, 04:27 AM UTC
- investigating Oct 30, 2025, 12:58 AM UTC
https://www.astronomer.io/docs/astro/deployment-health-incidents
- resolved Oct 30, 2025, 04:27 AM UTC
Deployment Health Incidents have been temporarily disabled.
Minor October 29, 2025 Astro UI performance may be severely degraded or unavailable 1h 1m Deployment Access, Deployment Access, Deployment Management, Deployment Management and 9 more
Started Oct 29, 2025, 11:57 PM UTC· resolved Oct 30, 2025, 12:58 AM UTC
- investigating Oct 29, 2025, 11:57 PM UTC
We are currently investigating this issue.
- investigating Oct 30, 2025, 12:51 AM UTC
Deployment Health Incidents may not be working https://www.astronomer.io/docs/astro/deployment-health-incidents
- monitoring Oct 30, 2025, 12:51 AM UTC
Deployment Health Incidents may not be working https://www.astronomer.io/docs/astro/deployment-health-incidents
- resolved Oct 30, 2025, 12:58 AM UTC
This incident has been resolved.
Critical October 29, 2025 Azure Front Door CDN issue causing timeouts to Astro Cloud UI 8h 44m Cloud UI, Cloud UI
Started Oct 29, 2025, 04:05 PM UTC· resolved Oct 30, 2025, 12:49 AM UTC
- investigating Oct 29, 2025, 04:05 PM UTC
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.
- monitoring Oct 29, 2025, 04:05 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Oct 29, 2025, 04:35 PM UTC
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/status
- resolved Oct 30, 2025, 12:49 AM UTC
Resolved per Azure status; https://azure.status.microsoft/en-us/status
Minor October 28, 2025 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 5h 46m Scheduling and Running DAGs and Tasks, Scheduling and Running DAGs and Tasks
Started Oct 28, 2025, 06:05 PM UTC· resolved Oct 28, 2025, 11:51 PM UTC
- investigating Oct 28, 2025, 06:05 PM UTC
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.
- monitoring Oct 28, 2025, 07:39 PM UTC
Customer deployments should no longer be affected, we are monitoring to confirm resolution.
- resolved Oct 28, 2025, 11:51 PM UTC
This incident has been resolved.